>> - Keep on using hg.exit1.org as the main source repository, but set it up
>> to automatically push changes to berlios.de, and use the HTTP server
>> there for anonymous read access.
>
>This one is a good match.
>My plan (of course susceptible to discussion and adjustements) is to use
>hg.berlios.de as reference repository, hosting stable branches, official
>tarballs, announcements. etc.
>To make a long story short, I see berlios as our frontend to the public.
>
>The backend, the place where actual development, discussion, proposals,
>experimental code, will still be hg.exit1.org.
Sounds good to me, as long as Joern doesn't have any problem with it. (:
>> So what I'm thinking would be useful is to:
>> (1) Move everything from transcode/trunk/ up to the root directory.
>[...]
>
>I 99% agree. The only 1% left is that I'd like to have the chance to
>host different subtrees on the same repo (see svn on berlios.de for
>example, the tcrund and transcode trees).
>In other words, I'd like to not be forced to start a new repo for a
>related project, e.g. tcrund.
>
>I've to admit that I've not yet grasped HG enterely (not even finished
>the hg book :( ), so it's possible my concern has no real foundation.
I haven't actually read the hg book in its entirety myself (just skimmed
enough to understand the differences from CVS/SVN), but it looks like hg
was designed with the idea of having multiple repositories per project.
That said, all the examples of multi-repository development use local
paths rather than remote ones, so I'm not quite sure the hg developers
thought that all the way through...
In any case, I wouldn't have a problem with keeping other tools in the
same project, and we could share common libraries like libtc that way as
well. We probably don't need to think about it immediately, but maybe
rename the "src" directory to "transcode", and move all the module
directories (encode/export/filter/import/multiplex) under that?
Old path New path
-------- --------
(root)/encode/* (root)/transcode/encode/*
(root)/export/* (root)/transcode/export/*
(root)/filter/* =====> (root)/transcode/filter/*
(root)/import/* (root)/transcode/import/*
(root)/multiplex/* (root)/transcode/multiplex/*
(root)/src/* (root)/transcode/*
Or if you don't like mixing files and directories at the same level, we
could make a separate directory "transcode/core" and move "src" there
instead.
>Full ack for (2) and (3).
Okay, I'll start on those changes... but probably tomorrow morning,
since it's past 2am here in Japan and I need sleep. (: I'll make a post
to -devel when I start rebuilding the repository, then let Joern know
when the new repository is ready. Alternatively -- Joern, do you know
whether it'd be possible for me to do something like:
hg clone /usr/local/src/transcode-new ssh://hg.exit1.org/transcode-new
and have you replace the "transcode" repository with the "transcode-new"
one once it's up?
>As for forwarding changes to berlios, I've no strong opionions yet.
>*Perhaps* is better to start pushing manually.
That'd be fine with me, and yeah, probably a good idea until we're used
to the new setup. (Though it should only be a matter of adding commit
and incoming hooks to push the changes out.)
--Andrew Church
achu...@achurch.org
http://achurch.org/
