(Almost) all extensions together in one place

Greg Ward greg at gerg.ca
Thu Mar 31 20:30:56 CDT 2011


On 31 March 2011, timeless said:
> On Thu, Mar 31, 2011 at 4:53 AM, Greg Ward <greg at gerg.ca> wrote:
> >  * give Mercurial developers a place to play around with subrepos
> 
> that's good. my first complaint is that hgweb sucks for not telling me
> about them.

Ironically, I deliberately chose to put absolute repo URLs in .hgsub
because I did not want to clutter up hg.gerg.ca's front page with 40
or 50 or 60 clones of other people's extensions.  And because I don't
want to maintain all those clones.  But now I'm stuck with "hg push"
recursing over 37 subrepos that I have no intention of committing or
pushing to. Count me in as another vote for read-only subrepos!

> missing: a script to analyze hgrc for unknown extensions.
> 
> I have about 1000 repositories floating around, distributed on
> probably 10 computers.
> 
> If I could run a script which would try using each hgrc it finds and
> use that to identify extensions which the repository doesn't know,
> that'd be great.

Hmmmm.  I want to limit this to extensions with a cloneable URL on the
public Internet.  I'm sure there are bazillions of private extensions
out there that implement XYZ Corp's own weird policy, but they are out
of scope for allextensions.

So your hypothetical 'missing' script could find extensions you have
configured, and if you have configured by pointing extensions.foo at
your local clone of foo, and that clone has paths.default set, then we
can guess "ah-ha! here is a URL for the foo extension".  But then it
will take some sort of intervention to decide if that URL is suitable
for adding to allextensions.

OTOH, maybe I should just stick with my current restrictive policy: if
it's not listed in the Mercurial wiki, it doesn't go in allextensions.

> Bonus points for there to be a safe way for me to clone only that
> script and the list of known repositories without having to clone all
> of the subrepos. -- no i haven't spent the time playing with subrepos
> to know if this will happen by default -- I do *not* want to have to
> download all extensions just to tell you what i have that you don't :)

Well, if you happen to have a copy of Mercurial 1.2 (pre-subrepos)
around you could clone it with that.  ;-)

> I know you want someone to add things to a wiki, but at the moment i'm
> cursing wikis and rebasing ~50 mq items.

Yeah, my secret agenda here is to get people to agree on some common
metadata for extensions in the wiki.  Here is my proposal:

  Repository: <public http url that I can pass to hg clone>
  Other info: <public http url to blog post, project home page, wiki, whatever>

Every extension should provide "Repository".  Many extensions commonly
use "Download site" for the cloneable URL, which I think is
misleading.  I propose changing every occurrence of "Download site"
that references a cloneable URL to "Repository".

If no one objects, I'll probably do some incredibly tedious and
mind-numbing wiki-search-and-replace over the weekend.  Wheeee fun.

        Greg
-- 
Greg Ward                                http://www.gerg.ca/
I don't believe there really IS a GAS SHORTAGE.. I think it's all just
a BIG HOAX on the part of the plastic sign salesmen -- to sell more numbers!!


More information about the Mercurial-devel mailing list