On Tue, Apr 12, 2016 at 01:50:28PM -0000, Martin Packman wrote:
> Martin Pitt: We currently don't have lxd as a dep on this package
> because it's included by default on the image.
This is not a justification for omitting the dependency. If the juju
package relies on lxd for its core functionality, it should be declared as a
dependency, even if the lxd package is installed by default. The only
exceptions to this rule are packages declared Essential: yes.
> If I add it (as a depends, or recommends), does that mean our autopkgtests
> including the lxd provider ones will run on new lxd package uploads and
> prevent them entering the archive in future?
Yes. (Which, I hope it's clear, is the desired behavior for autopkgtests.)
On Tue, Apr 12, 2016 at 01:50:28PM -0000, Martin Packman wrote:
> Martin Pitt: We currently don't have lxd as a dep on this package
> because it's included by default on the image.
This is not a justification for omitting the dependency. If the juju
package relies on lxd for its core functionality, it should be declared as a
dependency, even if the lxd package is installed by default. The only
exceptions to this rule are packages declared Essential: yes.
> If I add it (as a depends, or recommends), does that mean our autopkgtests
> including the lxd provider ones will run on new lxd package uploads and
> prevent them entering the archive in future?
Yes. (Which, I hope it's clear, is the desired behavior for autopkgtests.)