All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: some trivial(?) questions about packagegroups
Date: Fri, 26 Mar 2021 11:45:06 -0400 (EDT)	[thread overview]
Message-ID: <117b58d-f7c6-6187-dc33-66d75292cc58@crashcourse.ca> (raw)


  what should be easy questions about packagegroups, inspired by my
running across some puzzling packagegroup recipes in my travels
recently. (i'll start with examples out of oe-core).

  first, as with any other recipe, given a "trivial" packagegroup
like, say, packagegroup-core-eclipse-debug.bb:

  SUMMARY = "Remote debugging tools for Eclipse integration"

  inherit packagegroup

  RDEPENDS_${PN} = "\
    gdbserver \
    tcf-agent \
    openssh-sftp-server \
    "

there is no need to add a "PROVIDES" line since every recipe file
automatically provides its own name. so far, so good.

  if we move up to packagegroup-core-nfs.bb, note how this recipe file
defines two additional packagegroups, and has to add a PROVIDES line
in order to make those new names accessible:

  PROVIDES = "${PACKAGES}"
  PACKAGES = "${PN}-server ${PN}-client"

  SUMMARY_${PN}-client = "NFS client"
  RDEPENDS_${PN}-client = "nfs-utils-client"

  SUMMARY_${PN}-server = "NFS server"
  RDEPENDS_${PN}-server = "\
    nfs-utils \
    nfs-utils-client \
    "

so the question is, must one supply a PROVIDES line for any
packagegroup names above and beyond the one that comes with the recipe
file itself? i ask what seems like a dumb question as i've run across
packagegroup recipe files that define multiple additional
packagegroups, but do not add them to the PROVIDES line. what is that
supposed to represent?

rday

             reply	other threads:[~2021-03-26 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 15:45 Robert P. J. Day [this message]
2021-03-26 19:22 ` [OE-core] some trivial(?) questions about packagegroups Andre McCurdy
2021-03-27 10:31   ` Robert P. J. Day
2021-03-27 19:54     ` Andre McCurdy
2021-03-27 20:13       ` Robert P. J. Day
2021-03-29  8:08   ` Robert P. J. Day

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=117b58d-f7c6-6187-dc33-66d75292cc58@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.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.