This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Grabbing XFree86.org's xc/ tree using cvsup
- From: Harold L Hunt II <huntharo at msu dot edu>
- To: cygwin-xfree at cygwin dot com
- Cc: xserver at pdx dot freedesktop dot org
- Date: Sat, 01 Nov 2003 17:55:36 -0500
- Subject: Grabbing XFree86.org's xc/ tree using cvsup
- Reply-to: cygwin-xfree at cygwin dot com
I am looking into how to import the XFree86.org xc/ tree into
freedesktop.org. It looks like cvsup is the way to go here, since it
mirrors the actual repository instead of grabbing a snapshot of the
repository.
My question is: should I tell cvsup to drop the tree directly into
/home/cvs, or should I pull the tree into my home directory, then copy
it into /home/cvs?
It sort of seems unwise to drop the tree directly into /home/cvs,
especially since cvsup needs to keep some state files (which I would
most likely put in /home/harold/xc/sup) that imply that only one person
would be able to make changes to the cvsup mirror.
Another thing to keep in mind is how we want to do development. It has
been suggested that we keep the HEAD branch in sync with XFree86.org and
that we do our development on another branch. The question here is
whether cvsup can preserve a local branch of the code and still be used
to sync with XFree86.org. I doubt that this is the case, since cvsup is
essentially mirroring the files, not branches/tags/etc. Does this mean
that we must manually track XFree86.org and apply their patches after
the initial import?
I would appreciate any input on this. Let me be the first to admit that
I am not a CVS administrator. I want to get this tree setup quickly so
that Alexander Gottwald (ago), Kensuke Matsuzaki (zakki), and myself can
quickly resume our development on Cygwin/X. Another goal is for the
xc/ tree to be usable by others that wish to develop on an old-style xc/
tree outside of XFree86.org.
Thanks in advance,
Harold