Re: How does team maintenace of python module works?
Am 20.02.2013 09:31, schrieb Thomas Goirand:
> On 02/20/2013 12:38 PM, Scott Kitterman wrote:
>> On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote:
>>> The idea to use "git archive" was mostly from Julien Danjou. It's
>>> very nice because that way, we can use xz compression, instead
>>> of what upstream provides (that is, github .zip or .tar.gz, which
>>> isn't the best).
>> See devref 6.7.8. This not an appropriate reason to not use the upstream
>> tarball.
>>
>> Scott K
> Thanks Scott, but I believe I know what I'm doing.
No, I don't think so.
> This wasn't the
> only reason I stated, it's only one of the consequences.
>
> What upstream considers "release tarballs" are *not* what Github
> provides anyway (it is a little bit more complex than this).
So there would be no way anymore to build using upstream tarballs? This doesn't
sound appropriate to force on a whole team.
I don't think that many of the people that voted are aware of your implicit
changes (no release tarballs, including upstream source in the VCS) by moving to
git.
Matthias
Reply to: