From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [RFC v1 1/1] Reorder and -dev
Date: Mon, 21 May 2012 06:45:35 -0700 [thread overview]
Message-ID: <4FBA46FF.8050700@linux.intel.com> (raw)
In-Reply-To: <34ED02DB-EE8A-4F76-BD6B-2CE2456B1EB7@dominion.thruhere.net>
On 05/21/2012 03:57 AM, Koen Kooi wrote:
>
> Op 21 mei 2012, om 12:48 heeft Otavio Salvador het volgende geschreven:
>
>> On Mon, May 21, 2012 at 3:53 AM, Martin Jansa<martin.jansa@gmail.com> wrote:
>>> the rest looks ok, but I'm pretty scared from such changes, does your
>>> buildhistory diffs show just *-config file moves or something else too?
>>
>> It would be nice if some images could be build before and after the
>> patch and check before proposing this for merging.
>
> Indeed, run the buildhistory output through Pauls analysis tool and share the results.
>
Yes, I plan too once I get closer to done, I know it will move more than
the -config files, biggest issue I have seen so far are extensions and
modules that might live in ${libdir}/${BPN}/...*.so vs *.so.* I believe
that most of these .so libraries live in the standard base package, not
the -dev package.
Sau!
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-05-21 13:55 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 [this message]
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
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=4FBA46FF.8050700@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox