how are release tarballs generated?
Faheem Mitha
faheem at faheem.info
Tue Jan 13 11:50:36 CST 2015
Hi Matt,
On Tue, 13 Jan 2015, Matt Mackall wrote:
> On Tue, 2015-01-13 at 17:43 +0530, Faheem Mitha wrote:
>> Hi,
>>
>> How are the source tarballs which are put on the site for download
>> generated? The tarball generated by
>>
>> python setup.py sdist
>
> Are you looking for an opinion on setuptools? I sure have one.
Not especially. But feel free, regardless.
I'm mildly curious why 'make dist' works (I checked), and 'python setup.py
sdist' doesn't, in case anyone cares to enlighten me. For example, the
latter does not put the 'hgeditor' file in the tarball.
> I do this:
> hg co -q $1
> make doc > /dev/null
> make dist-notests
> Check out the makefile entry for dist-notests.
Thanks. I just did 'make dist' and it produced a usable tarball. I'll keep
'make dist-notests' in mind.
Maybe it would be reasonable to document this somewhere in the source? I'm
not sure where, though.
Regards, Faheem
More information about the Mercurial-devel
mailing list