On Thu, Apr 30, 2020 at 10:27:30AM +0200, Andrea Bolognani wrote:
> On Wed, 2020-04-29 at 10:21 +0100, Daniel P. Berrangé wrote:
> > On Wed, Apr 29, 2020 at 11:10:41AM +0200, Andrea Bolognani wrote:
> > > So what I think we need is an additional flag that can be used to
> > > choose one of the two
On Wed, 2020-04-29 at 10:21 +0100, Daniel P. Berrangé wrote:
> On Wed, Apr 29, 2020 at 11:10:41AM +0200, Andrea Bolognani wrote:
> > So what I think we need is an additional flag that can be used to
> > choose one of the two possible behaviors. This wouldn't be limited
> > to the Dockerfile generat
On Tue, Mar 31, 2020 at 03:28:20PM +0100, Daniel P. Berrangé wrote:
> Currently when creating a Dockerfile for a container, we include the
> full set of base packages, along with the packages for the project
> itself. If building a Perl binding, this would require us to install
> the base package,
On Wed, Apr 29, 2020 at 11:10:41AM +0200, Andrea Bolognani wrote:
> On Tue, 2020-03-31 at 15:28 +0100, Daniel P. Berrangé wrote:
> > Currently when creating a Dockerfile for a container, we include the
> > full set of base packages, along with the packages for the project
> > itself. If building a
On Tue, 2020-03-31 at 15:28 +0100, Daniel P. Berrangé wrote:
> Currently when creating a Dockerfile for a container, we include the
> full set of base packages, along with the packages for the project
> itself. If building a Perl binding, this would require us to install
> the base package, libvirt
Currently when creating a Dockerfile for a container, we include the
full set of base packages, along with the packages for the project
itself. If building a Perl binding, this would require us to install
the base package, libvirt packages and Perl packages. With the use
of the "--inherit libvirt-f
