From: "Sinan Kaya" <okaya@kernel.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta-oe][PATCH v2] procps: split into binary subpackages
Date: Tue, 1 Dec 2020 09:39:41 -0500 [thread overview]
Message-ID: <63d2d693-dece-0c94-87f9-7965cbb56686@kernel.org> (raw)
In-Reply-To: <CAP9ODKoT12CUNKJnqT_edYu3-Ei-zganQzskRx47OLrJWwXcEQ@mail.gmail.com>
On 12/1/2020 9:30 AM, Otavio Salvador wrote:
>>>> I am starting to get a little worried about the direction these
>>>> patches
>>>> are heading in. How much of the system are we going to split into
>>>> individual package per binaries?
>>> I am wondering why this is a concern for you? If we keep the old
>>> package rdepends on the new ones I see no problem in allowing this
>>> granular packaging.
>> Taking this to a conclusion its heading towards, most recipes
>> generating more than one binary would end up with this splitting code.
>> I don't like having large blocks of python in each recipe and heading
>> that way means we should probably change approach somehow.
>>
>> My worry is that simpler recipes are easier to maintain, test and
>> upgrade.
> Maybe Sinan could try to rework this and move the python code to a
> class reducing code duplication?
The problem I'm trying to solve is I only need ps file out of this
entire package. Everything else in this package is useless for me. I'm
sure no-one wants dead code in their system especially if they are size
constrained.
Ideal solution would be to have --with/without-foo support upstream
that we can configure with PACKAGECONFIG.
I'm happy to look at other options if there is an alternative.
next prev parent reply other threads:[~2020-12-01 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 3:43 [meta-oe][PATCH v2] procps: split into binary subpackages Sinan Kaya
2020-12-01 10:37 ` [OE-core] " Richard Purdie
2020-12-01 11:29 ` Otavio Salvador
2020-12-01 14:15 ` Richard Purdie
2020-12-01 14:30 ` Otavio Salvador
2020-12-01 14:39 ` Sinan Kaya [this message]
2020-12-01 15:07 ` Richard Purdie
2020-12-01 16:49 ` 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=63d2d693-dece-0c94-87f9-7965cbb56686@kernel.org \
--to=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--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