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. t
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 multip
HI Michal,
2009/9/6 Michal Suchanek :
> The chroot_local-packageslists directory is created in the configuration
> but not used.
As far as I understand, it can be used manually. In between using
lh_config and lh_build I may add something to this directory. I agree
with the manual, in that ... con
Package: live-helper
Version: 1.0.5-1
Severity: normal
The chroot_local-packageslists directory is created in the configuration
but not used.
This is confusing for the users because at least some other directories
created in cthe configuration work automagically.
There are two ways how this can
