From: "Sinan Kaya" <okaya@kernel.org>
To: pb@pbcl.net
Cc: openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [meta-oe][PATCH v4 1/3] introduce lib_subpackage
Date: Fri, 4 Dec 2020 08:30:01 -0500 [thread overview]
Message-ID: <d7593470-039f-e4c4-e4a9-36c475cf99c0@kernel.org> (raw)
In-Reply-To: <20201204110142.GV30831@pbcl.net>
+Richard,
On 12/4/2020 6:01 AM, Phil Blundell via lists.openembedded.org wrote:
> 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?
I'm open to giving it a better name. Richard pointed me to a file
beginning with lib_foo.class for where this functionality could be
hosted before.
>
>> + 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?
I want to be able to include procps-ps without the entire procps
package. I was not able to do that without the above two lines.
>
> p.
>
>
>
>
>
next prev parent reply other threads:[~2020-12-04 13:30 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 ` [OE-core] [meta-oe][PATCH v4 1/3] introduce lib_subpackage Phil Blundell
2020-12-04 13:30 ` Sinan Kaya [this message]
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=d7593470-039f-e4c4-e4a9-36c475cf99c0@kernel.org \
--to=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox