From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC v1 0/1] Reorder ${PN} and ${PN}-dev
Date: Mon, 21 May 2012 17:05:50 +0100 [thread overview]
Message-ID: <1337616350.22747.19.camel@ted> (raw)
In-Reply-To: <CABcZAN=0JDHip7=E99Dh_mNUgkmtny5z0HbyEq0uh2_+-ehsUg@mail.gmail.com>
On Mon, 2012-05-21 at 08:54 -0700, Chris Larson wrote:
> On Mon, May 21, 2012 at 8:47 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
> > On 5/21/12 1:42 AM, Saul Wold wrote:
> >>
> >> This RFC is the first pass at reordering the above 2 items in
> >> the PACKAGES list. This is in part an out cropping of the bug
> >> #2367 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=2367),
> >> which show the miss packaged pcap-config file.
> >
> >
> > I've often wondered why the order is the way it is. If I were to do this
> > from scratch, I'd move the ${PN} item to last in the default order. Have
> > you considered this more radical approach, that would then allow all of the
> > default splits to occur before the ${PN} processing. (It might also allow
> > the ${PN} to simply be a "/*" instead of more complex rules.)
>
> This would be quite nice, if we could pull it off without breaking
> anything horribly.
-dev is likely the nastiest to move, the other two defaults aafter PN
are -locale and -doc, neither of which should present as much of a
challenge so we can probably move those. Its not likely to gain much
either though as we don't split the files in those directories like we
do with -dev files.
I'm not sure a '*' matching for PN is the most desirable default though,
in some ways I like the fact we have to specifically think about the
exceptions to the default rules...
Cheers,
Richard
prev parent reply other threads:[~2012-05-21 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:42 [RFC v1 0/1] Reorder ${PN} and ${PN}-dev Saul Wold
2012-05-21 6:42 ` [RFC v1 1/1] Reorder and -dev Saul Wold
2012-05-21 6:53 ` Martin Jansa
2012-05-21 10:48 ` Otavio Salvador
2012-05-21 10:57 ` Koen Kooi
2012-05-21 13:45 ` Saul Wold
2012-05-21 15:47 ` [RFC v1 0/1] Reorder ${PN} and ${PN}-dev Mark Hatle
2012-05-21 15:54 ` Chris Larson
2012-05-21 16:02 ` Saul Wold
2012-05-21 16:05 ` Richard Purdie [this message]
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=1337616350.22747.19.camel@ted \
--to=richard.purdie@linuxfoundation.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.