All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Phil Blundell" <pb@pbcl.net>
To: Sinan Kaya <okaya@kernel.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH v4 1/3] introduce lib_subpackage
Date: Fri, 4 Dec 2020 12:01:42 +0100	[thread overview]
Message-ID: <20201204110142.GV30831@pbcl.net> (raw)
In-Reply-To: <20201203232826.28519-1-okaya@kernel.org>

On Thu, Dec 03, 2020 at 11:28:24PM +0000, Sinan Kaya wrote:
> This subclass allows us to easily split a recipe into
> subpackages.

"lib_subpackage" seems a slightly odd name for something that isn't
dealing with libraries.  What's the etymology of that?

> +    d.appendVar("PACKAGES", " " + " ".join(packages))
> +    d.appendVar("PROVIDES", " " + " ".join(packages))

It seems a bit strange to be putting the same things in PACKAGES and
PROVIDES.  Is that actually necessary?

p.


  parent reply	other threads:[~2020-12-04 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 23:28 [meta-oe][PATCH v4 1/3] introduce lib_subpackage Sinan Kaya
2020-12-03 23:28 ` [meta-oe][PATCH v4 2/3] net-tools: split into binary packages Sinan Kaya
2020-12-03 23:28 ` [meta-oe][PATCH v4 3/3] procps: split into binary subpackages Sinan Kaya
2020-12-04 11:01 ` Phil Blundell [this message]
2020-12-04 13:30   ` [OE-core] [meta-oe][PATCH v4 1/3] introduce lib_subpackage Sinan Kaya
2020-12-05 22:23     ` Phil Blundell
2020-12-06  0:54       ` Sinan Kaya
     [not found]       ` <164DFA8489EB0A7A.29396@lists.openembedded.org>
2020-12-09 23:47         ` Sinan Kaya

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=20201204110142.GV30831@pbcl.net \
    --to=pb@pbcl.net \
    --cc=okaya@kernel.org \
    --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.