From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Sinan Kaya <okaya@kernel.org>,
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, 01 Dec 2020 14:15:14 +0000 [thread overview]
Message-ID: <0976a2df7109d102b71033dc444ba9414670d4aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKokNQw_HmiX6MC2wbB47tapHXC-9Za5tKzkbbtYsFHr6A@mail.gmail.com>
On Tue, 2020-12-01 at 08:29 -0300, Otavio Salvador wrote:
> Hello Richard,
>
> Em ter., 1 de dez. de 2020 às 07:37, Richard Purdie
> <richard.purdie@linuxfoundation.org> escreveu:
> > On Tue, 2020-12-01 at 03:43 +0000, Sinan Kaya 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.
Cheers,
Richard
next prev parent reply other threads:[~2020-12-01 14:15 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 [this message]
2020-12-01 14:30 ` Otavio Salvador
2020-12-01 14:39 ` Sinan Kaya
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=0976a2df7109d102b71033dc444ba9414670d4aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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