Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Apr 2015 09:08:53 +0200 (CEST)
From:      sg-ball@laposte.net
To:        Baptiste Daroussin <bapt@FreeBSD.org>
Cc:        freebsd-pkg@freebsd.org
Subject:   Re: Problem with pkg behind a chunking proxy
Message-ID:  <2106067877.31883344.1427872133869.JavaMail.zimbra@laposte.net>
In-Reply-To: <20150331223320.GJ30115@ivaldir.etoilebsd.net>
References:  <902242756.31277524.1427836544530.JavaMail.zimbra@laposte.net> <1476070491.31317997.1427838521190.JavaMail.zimbra@laposte.net> <20150331223320.GJ30115@ivaldir.etoilebsd.net>

next in thread | previous in thread | raw e-mail | index | archive | help
I could join to GitHub, fork pkg and commit the patch to my fork (https://g=
ithub.com/sg-ball/pkg), but it is still untested and I wonder if the displa=
y "file: 0%" that directly goes to 100% is acceptable.

Anyway, thanks for you quick anwser

Serge

----- Mail original -----=20
De: "Baptiste Daroussin" <bapt@FreeBSD.org>=20
=C3=80: sg-ball@laposte.net=20
Cc: freebsd-pkg@freebsd.org=20
Envoy=C3=A9: Mercredi 1 Avril 2015 00:33:20=20
Objet: Re: Problem with pkg behind a chunking proxy=20


> ...=20
> I think this feature could be interesting since Transfer-Encoding: chunke=
d is valid as HTTP 1.1 but I'm not used to submitting patches even if I've =
been using FreeBSD since release 3.x=20
...=20
So usually the feature should be discussed in pkg@FreeBSD.org or in #pkgng=
=20
(freenode) or on github issue, I have to confess that I do track more often=
=20
github issue tracker than freebsd's bugzilla for pkg related issues. (which=
 is=20
bad I should more track both).=20

Concerning your feature it is very welcome :) usually we do like pull reque=
st on=20
github. Note that you are just in time for pkg 1.5 which will be released s=
oon :)=20

The preferred way is usually pull request, but I'm flexible if the submitte=
r is=20
anti github then I can just grab patches.=20

That part of the code hasn't been modified since pkg 1.4 so the patch shoul=
d=20
apply just fine.=20

...=20

So as a conclusion first make a pull request on github, then once it is wel=
l=20
tested enough you can provide a patch for base (or I'll do) if so open a ti=
cket=20
in the bug tracker for base and do not hesitate to harass me :)=20

Thanks again,=20
Bapt=20






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2106067877.31883344.1427872133869.JavaMail.zimbra>