[EMAIL PROTECTED] wrote:
> Thanks.. this excatly what I was looking for. I didn't notice the -d option
> when I looked in the manual - silly me.. I don't quite understand what you
> mean with 'breaking reproducibility of old releases'. If you have a spare
> moment to explain this to me, it would be very nice.
This means that if you were using a structure like:
newmod -a newmod-1 newmod-2 newmod-3 newmod-4 newmod-5
newmod-1 -l -d top-dir top-dir
newmod-2 -d top-dir/java top-dir/java
newmod-3 -l -d top-dir/misc top-dir/misc
newmod-4 -d top-dir/java/images top-dir/misc/images
newmod-5 -d top-dir/java top-dir/javalib
from version 0.01 through 2.0 of your software and around 2.1 you decided not
to use javalib anymore so your new modules definitions were:
newmod -a newmod-1 newmod-2 newmod-3 newmod-4
newmod-1 -l -d top-dir top-dir
newmod-2 -d top-dir/java top-dir/java
newmod-3 -l -d top-dir/misc top-dir/misc
newmod-4 -d top-dir/java/images top-dir/misc/images
Then if you went and tried to use my_1_7_tag to check out version 1.7 of newmod
you wouldn't get the javalib directory and presumably the software wouldn't
work.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Welcome to the Church of the Holy Cabbage. Lettuce pray
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
