How to do source management?

[Kenn Humborg]

On Wed, Jul 28, 2004 at 09:56:02PM +0200, Jan-Benedict Glaw wrote:
> X-VAX-is-cool: Yes!
> Hi!
> 
> As you all already know from my previous email to you, I'm about to
> import toolchain's sources. Before that, I'd like to discuss the "how".
> 
> Please choose your weapons:
> 
> 	[ ] CVS
> 	[ ] Arch
> 	[ ] Subversion
> 	[ ] Other: _____________

I've only used CVS.  But I'm willing to learn.

> distance:
> 
> 	[ ] Just patch sources with whatever is mentioned in upstream
> 	    CVS status emails and check it in onto HEAD.
> 	[ ] Import patches into a separate upstream branch.
> 	[ ] Import snapshots into a separate upstream branch

Tough call.  I'm familiar with the 3rd option from importing Linus kernels
into the Linux/VAX CVS at SourceForge.  When it goes smoothly, it's great.
However, sometimes issues with SF's CVS server make it tricky for such
large source trees.

If you're going to use SF's CVS, I suggest not going with option 3.

> 
> and ammunition:
> 
> 	[ ] Import binutils, gcc and glibc into three modules reflecting
> 	    the three upstream modules. Con: IMHO hard to build, at
> 	    least I need to figure out how to do that at all:)
> 	[ ] Import binutils+gcc as a combined tree; most probably that
> 	    would make some sense if we used upstream snapshots then.
> 	    Pro: easy to build; Con: glibc is "extra" then.
> 	[ ] Other: _________

I don't really see how glibc being "extra" is a problem.  Surely it's 
pretty much a separate project within the FSF?

I'd suggest creating a local CVS/SVN/whatever repository and play around
with the various options yourself using a selection of recent FSF 
tarballs.

BTW, anyone have any objection to making the Reply-To: point to the list?

Later,
Kenn