Re: [PATCH] Add support for supplying more types of debian package relationships

[Henning Schild <henning.schild@siemens.com>]

Am Wed, 11 Sep 2019 11:32:08 +0200
schrieb "Dalamagkidis, Konstantinos (MO RS EN CCIT TEC AR)"
<konstantinos.dalamagkidis@siemens.com>:

> > On 11.09.19 10:41, [ext] Dalamagkidis, Konstantinos wrote:  
> > > We need to be able to specify other package relationships, such as
> > > Pre-Depends or Provides/Replaces/Conflicts.
> > >
> > > This change supports supplying DEBIAN_PREDEPENDS, DEBIAN_REPLACES,
> > > DEBIAN_CONFLICTS and DEBIAN_PROVIDES, as well as bitbake-style
> > > RDEPENDS or RDEPENDS_{PN} variables. The DEBIAN_* take priority.
> > >  
> >
> > This, as well as your DPKG_ARCH patch, is enhancing and further
> > establishing debianize.bbclase as an official interface. I already
> > urged Henning to do that - which includes writing documentation for
> > this. Your change here should extend that (not yet existing)
> > documentation as well.
> >
> > One of the thing to consider while designing & enhancing the recipe
> > API for debianize: We should not create something that is as
> > complex as writing Debian control files directly - or even more
> > complex than that.
> >
> > BTW, what kind of application packages are you generating for
> > dpkg-raw?  
> 
> We have ca 20 packages that use dpkg-raw, split more or less
> equally between configuration, scripts and some pre-built
> binaries. The conflicts/replaces is used in a couple of
> configuration packages. We are also porting recipes from a
> previous version that was using "plain yocto", so it is easier if
> we can just use RDEPENDS, RPROVIDES, etc. Personally I would
> prefer to use dpkg over dpkg-raw everywhere, but other colleagues
> find dpkg-raw easier.

My suggestion here is to keep that patch in your layer. You having that
problem 20 times does not make it common, 20 independent users would ;).

So you could put that magic into a dpkg-my-layer-yocto-glue class. The
deps in Isar are a pain, because we are dealing with two worlds. I
personally do not think that "pretending this away" is a good idea.

If you actually have configure + compile tasks in your dpkg-raw you are
on the wrong track and should stop pretending its yocto! Or at least
make sure all that gets done in buildchroot. If you want please explain
what you are doing, like Jan asked before.

Henning

> Rgds
> Konstantinos