pHi, when the chroot_local-packageslists behaviour was changed, i was not fan of that. however, it appears to be not that easy...
the problem: on the one hand, declaring that everything in chroot_local-packageslists is used automatically sucks, because then, if you have multiple lists for multiple types of images, you have to remove some files for every build, except the list that you're going to use. on the other hand, declaring that nothing in chroot_local-packageslists is used automatically is nice, because you can do a simple lh_config call in order to activate the list you want, and don't need to move arround files. otoh, it is inconsistent with the other config/* directories behaviour. means: for legacy reasons, we should not change the behaviour in live-helper 1.x. but for live-helper 2.x, i'd really like to get some way out of the above dillemma - any ideas welcome, i'm sort of out of ideas myself. ...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. anyway.. commends and better ideas wanted and welcome. -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
