All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Joslyn <robert.joslyn@redrectangle.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] pciutils: Move headers from pciutils-dev to libpci-dev
Date: Sun, 02 Dec 2018 17:42:00 -0800	[thread overview]
Message-ID: <1543801320.28866.12.camel@redrectangle.org> (raw)
In-Reply-To: <6f1b3209e6b40f0b796f68dd8c638bb0f89a241c.camel@linuxfoundation.org>

On Sun, 2018-12-02 at 10:43 +0000, Richard Purdie wrote:
> On Sat, 2018-12-01 at 19:14 -0800, Robert Joslyn wrote:
> > The pciutils recipe places libpci in a separate package, but the
> > default
> > package split puts the headers for the library in pciutils-dev.
> > When
> > building an SDK for an image that uses libpci, but not pciutils,
> > the
> > headers for libpci are not included.
> > 
> > Move the headers, unversioned so symlink, and pkgconfig files from
> > pciutils-dev to libpci-dev so the SDK gets those files for images
> > using
> > libpci.
> > 
> > Signed-off-by: Robert Joslyn <robert.joslyn@redrectangle.org>
> > ---
> >  meta/recipes-bsp/pciutils/pciutils_3.6.2.bb | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/meta/recipes-bsp/pciutils/pciutils_3.6.2.bb
> > b/meta/recipes-bsp/pciutils/pciutils_3.6.2.bb
> > index 413421cd8a..de1e54e5a5 100644
> > --- a/meta/recipes-bsp/pciutils/pciutils_3.6.2.bb
> > +++ b/meta/recipes-bsp/pciutils/pciutils_3.6.2.bb
> > @@ -52,9 +52,11 @@ do_install () {
> >  	oe_multilib_header pci/config.h
> >  }
> >  
> > -PACKAGES =+ "${PN}-ids libpci"
> > +PACKAGES =+ "${PN}-ids libpci libpci-dev"
> >  FILES_${PN}-ids = "${datadir}/pci.ids*"
> >  FILES_libpci = "${libdir}/libpci.so.*"
> > +FILES_libpci-dev = "${includedir} ${FILES_SOLIBSDEV}
> > ${libdir}/pkgconfig"
> >  SUMMARY_${PN}-ids = "PCI utilities - device ID database"
> >  DESCRIPTION_${PN}-ids = "Package providing the PCI device ID
> > database for pciutils."
> >  RDEPENDS_${PN} += "${PN}-ids"
> > +RDEPENDS_libpci-dev = "libpci (= ${EXTENDPKGV})"
> 
> "dev" packages per library don't really work unfortunately as most
> code
> can't be split like that.
> 
> The general policy is one dev package per recipe. This patch doesn't
> just move things but creates a new package.
> 
> The dev-pkgs code should be resolving "libpci" back to "pciutils" and
> from there it can figure out it should be adding pciutils-dev, that
> is
> the real bug we need to fix.
> 
> Cheers,
> 
> Richard


Hi Richard,

The reason I thought to create a libpci-dev package was because if
there is only pciutils-dev, it means the other things in pciutils are
then pulled into the SDK that you may not care about. Not that big a
deal with the SDK, but it seemed better to avoid it. I can see it being
fairly annoying to split out multiple *-dev packages for more complex
recipes though.

I'm not familiar with the packaging code, but I can try to take a look
at what it would take to tie the dev-pkgs dependency back to the the
single -dev package for the recipe.

Thanks,
Robert


      reply	other threads:[~2018-12-03  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02  3:14 [PATCH v2] pciutils: Move headers from pciutils-dev to libpci-dev Robert Joslyn
2018-12-02 10:43 ` Richard Purdie
2018-12-03  1:42   ` Robert Joslyn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1543801320.28866.12.camel@redrectangle.org \
    --to=robert.joslyn@redrectangle.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.