On Fri, Jul 18, 2014 at 10:31 AM, Scott Moser <email address hidden> wrote:
> deciding to install a package should not *break* other packages.
> thats the problem we have.
>
> the images are built to be generic. they don't have specific target
> when their built. and this is the only point where they have to know
> that target at "package selection time". Everything else just works.
>
> The bug is easily recreated on a system that should not use flash-kernel:
> $ apt-get install flash-kernel
> $ upate-initramfs
> FAIL
>
> thats a bug. installing 1 package should not break another.
Right, I'd agree that the hook shouldn't error out if a package
outside the dependency chain is not installed. Though big flashing
warnings that you're possibly about to make your system unbootable
would seem be appropriate.
On Fri, Jul 18, 2014 at 10:31 AM, Scott Moser <email address hidden> wrote:
> deciding to install a package should not *break* other packages.
> thats the problem we have.
>
> the images are built to be generic. they don't have specific target
> when their built. and this is the only point where they have to know
> that target at "package selection time". Everything else just works.
>
> The bug is easily recreated on a system that should not use flash-kernel:
> $ apt-get install flash-kernel
> $ upate-initramfs
> FAIL
>
> thats a bug. installing 1 package should not break another.
Right, I'd agree that the hook shouldn't error out if a package
outside the dependency chain is not installed. Though big flashing
warnings that you're possibly about to make your system unbootable
would seem be appropriate.