Hi,
Thanks very much for your response and your help. I will enter
comments and questions below.
Bill
"Greg A. Woods" wrote:
>
> [ On Monday, February 28, 2000 at 11:34:19 (-0500), William Lewis Brown wrote: ]
> > Subject: Private repositories v.s. Open Source repositories
> >
> > I need to have a section of an open source project's code in my own
> > private repository. The open source project uses CVS and so do I. I
> > want to know how people typically work with this type of an
> > environment. I have included two suggestions below.
>
> Is the "open source" project's repository available by FTP or better yet
> by CVSup? If so then with CVSup you can easily use a locally kept copy
> of it (you'll need two copies of it and a local CVSup server if it is
> only available by FTP) to tag local releases.
I have not heard of CVSup nor of course used it. It sounds like the
type of tool for which I am searching. Thanks for the reference.
I am working with the Mozilla sources. I don't know yet if they
support any distribution of the ",v" files. The default answer is no.
>
> >From there you can simply "cvs import" into a module in your local
> working repository and treat that module as any other vendor-branched
> module might be. (I.e. keep your local changes on the trunk.)
I don't really know what you mean by a "vendor-branched" module. Could
you explain?
> I've done this successfully many times with the entire FreeBSD
> distribution (including X11 src and "ports").
What happens when I need to update the ",v" files from the remote
repository after I have added my changes into the trunk? Does CVSup
just do the right thing? Since I don't really know what the right thing
is, please tell me. For example, assume that version 1.9 of file X was
created as the result of a merge of my changes into version 1.8 from the
remote repository. If the remote repository has a version 1.9 distinct
from my own 1.9, what happens during the next download of the ",v"
files, via CVSup??, from the remote repository? Thanks.
>
>
> I do something similar on a regular basis with the NetBSD repository
> too, but until recently it was not available directly but only as a
> daily image of a "cvs update"ed workspace. In this case I use "sup" to
> keep a local copy of this "-current" workspace. You can't actually tag
> such a thing but given that the "cvs update" on the sup server is run
> daily at approximately the same time I just use the sup date to
> formulate the tag name for the "cvs import" that I do to my local
> repository.
Do your changes survive this operation as well?
>
> In either example the basic ideas are simple:
>
> 1. create your own "releases" of the open source project, perhaps even
> by using daily snapshots of their development branch;
>
> 2. import those releases to a vendor-branched local repository
> and do local development just as you would with any other
> vendor-branched module.
>
> The only major caveat here is that you can't easily use normal CVS
> branches in a vendor-branched module, at least not so long as you expect
> the normal "features" of a vendor branched module to continue to work
> properly.
I don't really know to what features your refer.
>
> --
> Greg A. Woods
>
> +1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
> Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
--
William L. Brown
Work: 603-465-2114
Fax: 603-465-2114
Cell: 617-803-9156
Email: [EMAIL PROTECTED]
Home: 603-465-2948
