[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Multiple branches in third party sources

From: Jeremie Le Hen
Subject: Multiple branches in third party sources
Date: Tue, 6 Dec 2005 23:14:44 +0100
User-agent: Mutt/1.5.11


[ please Cc: me when replying since I'm not subscribed to this list ]

I don't know if the subject is really accurate, but here is a
small description of my problem :

I am a FreeBSD user.  Contrary to Linux, FreeBSD is not a single kernel,
but a whole operating system, including some softwares (which means
those are not installed as packages, they _are_ shipped with FreeBSD).
This leads to have /etc containing a bunch of files that are always here.

I want to use CVS to import /etc as third-party sources and then create
a branch for each of my box.  Thus when upgrading FreeBSD to a newer
version, I would import the new /etc and merge the changes back to the
other box' branches.

FreeBSD has multiple major branches, most common ones are RELENG_4 (4.x),
RELENG_5 (5.x), RELENG_6 (6.x) and HEAD (7.x).  Most of my boxes run
RELENG_6 (the latest major release), but I still have one RELENG_4 and
another running HEAD.

I am wondering if I have to create one module per major FreeBSD branch,
or if it would be better to keep them all in a single module but with a
different vendor branch name upon import.  I can't indeed import 4.x
first, then 6.x and finally 4.x again all in the same branch, when I
will have to upgrade my 4.x box.

I hope I have been clear enough and that you will be able to answer me.

Thank you.

Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >

reply via email to

[Prev in Thread] Current Thread [Next in Thread]