RE: a question about defining modules
> Any recommendations on documentation other than "man configure" to figure > out how to use configure? bleah: http://www.gnu.org/directory/autoconf.html so-so: http://www.amazon.com/exec/obidos/asin/1565921127 better: http://www.amazon.com/exec/obidos/ASIN/1578701902 I'd be interested if others have better suggestions... ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: a question about defining modules
>Message: 4 >Date: Tue, 27 Aug 2002 07:52:40 -0400 >To: Isaac Claymore <[EMAIL PROTECTED]>,[EMAIL PROTECTED] >From: "Frederic Brehm" <[EMAIL PROTECTED]> >Subject: Re: a question about defining modules > >At 04:04 AM 8/27/2002, Isaac Claymore wrote: > > My situation is: 3 projects, A, B and C, share a common library > > X. They all need to make changes to libX, so I forked 3 branches > > from libX main trunk: branch-A, branch-B and branch-C. > > > Any hint or suggestion is greatly appreciated ;) > >Clay, > >CVS doesn't work very well as a configuration management tool. Use CVS to >save your source code. Use something else (configure, perhaps) to configure >the source to match the needs of the product during a build. > >Fred Fred: Any recommendations on documentation other than "man configure" to figure out how to use configure? thanks. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: a question about defining modules
At 04:04 AM 8/27/2002, Isaac Claymore wrote: > My situation is: 3 projects, A, B and C, share a common library > X. They all need to make changes to libX, so I forked 3 branches > from libX main trunk: branch-A, branch-B and branch-C. > Any hint or suggestion is greatly appreciated ;) Clay, CVS doesn't work very well as a configuration management tool. Use CVS to save your source code. Use something else (configure, perhaps) to configure the source to match the needs of the product during a build. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
a question about defining modules
Hi folks, I tried the following line in CVSROOT/modules: foo-1.0-a -r Release-1-0-branch foobar in hope that when I 'co foo-1.0', I'd get the Release-1-0-branch branch, since I had thought that CVS would do a simple textual substitution on alias modules, but it turned out not. My situation is: 3 projects, A, B and C, share a common library X. They all need to make changes to libX, so I forked 3 branches from libX main trunk: branch-A, branch-B and branch-C. The result is every time I 'co A', I'd also 'co -r branch-A libX'. Some simple client-side scripting will facilitate the process, but I don't wanna handle the varieties of my team members' platforms, thus I hope to find some server-side trick to do it. Any hint or suggestion is greatly appreciated ;) Clay -- Isaac Claymore /"\ASCII Ribbon Campaign Dawning Inc.\ /Respect for open standards Beijing, China X No HTML/RTF in email http://www.dawning.com.cn / \No M$ Word docs in email ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
