Hi KP Thanks for the quick reply
KP Kirchdoerfer wrote: ... >> >> I see that the release tag enables me to get a certain release level for >> apps and contrib. I believe that even the buildenv changes with >> releases. What is the canonical way to handle this? > > The buildenv doesn't change that often; but yes we should tag also. > >> is there a way to specify a different sources.cfg, to cater for multiple >> releases in multiple directories, but keeping a single buildenv? > > In conf/buildtool.conf you'll find: > > # name of the conf file with the source/package definitions > GlobalConffile = conf/sources.cfg Yes, that helps. I know you want to avoid branches in CVS. What is the canonical way to, let's say - replace openswan with strongswan and still track current kernel development/configuration.. or - have a slightly different set of kernel parameters... and yes, follow current development or - add a few applets to busybox Thanks Erich _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
