hg-extra for fedora

[Augie Fackler]

On Nov 10, 2010, at 7:41 AM, Mads Kiilerich wrote:

> On 11/10/2010 01:59 PM, Neal Becker wrote:
>> I'm planning to package some extra extensions for fedora.  My plan is to
>> call this hg-extra, and (to make my life simpler) to place them into
>> python/site-packages/hgextra.
> 
> There is no reason the extensions should live under site-packages. They are intended to be loaded by Mercurials extension loader and are not generally usable Python modules. (Mercurials extension loader will however use Pythons import function unless a source file is specified.)
> 
> I suggest putting the files in for example /usr/share/mercurial-pbranch/ and dropping a /etc/mercurial/hgrc.d/pbranch.rc with something like
> 
> [extensions]
> # pbranch = /usr/share/mercurial-pbranch/pbranch.py
> 
> Alternatively the package could place the extension files in _the_ hgext folder. That would allow simple configuration with just "pbranch=".

Putting them in the hgext folder feels like *really* bad advice - what happens if the extension becomes part of the tarball?

> 
>> For now this includes rdiff and pbranch.
>> 
>> Any thoughts?
> 
> OT: These examples are different upstream projects and should live in different packages - for example mercurial-rdiff and mercurial-pbranch.

As one that maintains far too many out of tree extensions, please do them as separate packages.

> 
> (IMHO rdiff is far from best practice not widely used, so I don't see much value in packaging it. But that won't and shouldn't stop you ;-))
> 
> /Mads
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel