On 27/08/15 18:20, Harald Dunkel wrote: > Hi Tomasz, > > On 08/23/15 14:56, Tomasz Buchert wrote: > > > > Hi Harri, as I wrote above - I don't want to endorse software packages > > outside Debian and doing what you proposed looks like that to me. > > Usually I would agree, but in this case its upstream providing a > Debian package. Can we ignore Debian packages provided by upstream?
Hi Harri,
well, let's call them "DEB packages provided upstream". We shouldn't
ignore them (whatever it means), but certainly we shouldn't embrace
them as they are. (More on that at the end).
>
> > What about Recommends?
> >
>
> "Recommends" sounds like something optional. I would guess that
> debocker doesn't work without either docker.io or lxc-docker, does
> it?
"Recommends" has the following meaning:
This declares a strong, but not absolute, dependency.
The Recommends field should list packages that would be found together with
this one in all but unusual installations.
What it means in practice - if you install debocker it will pull
docker.io by default (when "apt-get install" is executed), but also
apt-get will let you remove docker.io and install lxc-docker.
Sounds like really applicable here. Some small part of the
functionality of debocker is available without docker: you can build a
bundle.
>
> Using "Depends: docker.io | lxc-docker" docker.io is included by
> default, not to mention that there is no lxc-docker in the default
> Debian repositories.
>
> I am not sure at all why there are 2 docker packages. Did lxc-docker
> violate some Debian policies? Maybe the maintainers of docker.io and
> lxc-docker could agree upon a common virtual package name?
Notice, for example, that uploads to Debian have ~dfsg prefix: this
means that the source has to be repackaged to adhere to DFSG. I'm
pretty sure (although I haven't tested) that other policies are
violated too.
Having a virtual package that provides docker is doable, of course,
but is not needed really. And it won't change this one thing:
lxc-docker is not supported by Debian.
>
> Regards
> Harri
>
Now, let us focus on the practical aspect. We have two solutions:
1) Depends: docker.io | lxc-docker
2) Recommends: docker.io
I strongly favor 2) and I don't think there is any disadvantage wrt 1).
With 1) you do:
dpkg -i lxc-docker.deb
apt-get install debocker
or
apt-get install debocker
dpkg -i lxc-docker.deb
With 2) you do:
dpkg -i lxc-docker.deb
apt-get install --no-install-recommends debocker
or
apt-get install debocker
dpkg -i lxc-docker.deb
(I'm not even sure that --no-install-... is required, this really
depends how dpkg and friends handle such situation).
Let me know what you think.
Tomasz
signature.asc
Description: Digital signature
