Hi,
We are developing Java software and using a lot of open source components
that are all available through anon CVS. I've been thinking about how
to track these components; optimally, I'd like to stay in sync with the
"public" CVS development, while at the same time allowing local patches
to be CVS-managed. At the same time, as CVS trees of open source projects
are typically in flux, especially quality-wise, we'd need to be able to
select baselines - versions that are stable enough for our purposes.
I've tried a couple of approaches, but none are really satisfactory (I
can post my ideas here, but I really don't like what I've written up
so far about it). Are more people in this situation, and if yes: are
there workable solutions?
--
Cees de Groot http://www.cdegroot.com <[EMAIL PROTECTED]>
GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD 1986 F303 937F E098 9E8B
Forge your CipherSaber and list it: http://www.xs4all.nl/~cg/ciphersaber/
