I agree that this behaviour is awkward and I've had a similar problem with multiple builds.
> ...except one (which sucks somehow as well, though): we could request > packages lists to be named with a particular extensions, e.g. we would > only use chroot_local-packageslists/*.list automatically. that would > allow to have other files in there that are not used, and could teach > lh_config to 'activate' packageslists by renaming them. > .. or maybe an easier solution is to keep different directories with different packageslists with a common meaningful extension .. and then activate different packagelists by linking or renaming to the required directory. i.e. chroot_local-packageslists.xfce-openoffice chroot_local-packageslists.kde chroot_local-packageslists.kde-openoffice could be three useful builds ... and you could link one of them to 'chroot_local-packageslists' to activate it. I think I tried this once and the link did not work and I had to 'copy' instead which was not the best since you could fall into the trap of modifying the copy and not the 'source'. I did not want to 'move' since you could easily forget how to 'unmove' later .. unless it's built into lh_config somehow. Harold -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
