[Pkg-xen-devel] SCM and Mailing list input [u]

[Ralph Passgang]

Am Dienstag, 14. Februar 2006 20:29 schrieb Julien Danjou:
> On Tue, Feb 14, 2006 at 10:03:38AM -0800, Jeremy T. Bouse [c] wrote:
> >     First of all, I'd like to work on general consensus so I'd like to
> > see what people think of having the list setup to reply back to the
> > list. I know some lists use this and some don't so I'd like to get input
> > on the matter.
>
> List reply.

*ack*

> >     I'd also like to get input on choice of SCM to use, whether we
> > should stick to a centralized SCM like svn or cvs; or should we go
> > distributed and use mercurial as xen upstream does?
>
> Personnaly, like I wrote to you, I use Subversion, so it will be quicker
> for me if we use it, than to discover another SCM. But if something like
> mercurial can help us (and I don't have enough information right now to
> know this) and is better for our work, I am not against learn another
> software.

I don't really have a favourite scm myself, so csv/svn/mercuial is all fine 
for me.

but maybe there are two (small) things that would be against mercurial:

- mecrucial is not available for debian sarge (I know, not a hard task to 
backport it).

- mecrurial seems to blow a repository a lot.
I think this related to the amount of files that are in the repository (so for 
just the /debian directory this would probably not a real problem). At least 
a xen unstable tree with all .hg-stuff is about 60 - 70mb in size. a clean 
xen source + debian directory without any mercurical stuff in only 3,8 - 
4,2mb. of course the 60-70mb doesn't need to get transfered over the internet 
all the time, but in real life a lot of people don't care and always check 
out the whole tree again and again instead of just updating the local copy. 

but of course the fact that xen uses mercurial is something that would 
recommend mecurial for the /debian stuff too.

If someone wants to checkout xen and after that the /debian repository then 
only one tool is needed and maybe in future we could also try to merge the 
debian directory with the original xen upstream, because that would help to 
always keep the debian support close to the upstream.

It's not realistic to believe that not for more or less every new xen version 
also at least some files in the debian subdir needs an update. it could help 
to do that directly in xen unstable, I think. But I don't know if Ian Pratt 
and all others also would like to see that happen in future. But maybe it's 
better to do one step after the other ;-P

--Ralph

> This was my 2c,
>
> Regards,