From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Bringing an image from OE to OE-Core
Date: Tue, 4 Oct 2011 17:43:17 -0500 [thread overview]
Message-ID: <4E8B8C05.5050508@windriver.com> (raw)
In-Reply-To: <4E8B6D47.9000600@intel.com>
On 10/4/11 3:32 PM, Saul Wold wrote:
> On 10/04/2011 01:27 PM, Philip Balister wrote:
>> On 10/04/2011 04:08 PM, Saul Wold wrote:
>>> On 10/04/2011 12:58 PM, Philip Balister wrote:
>>>> I'm about to start bringing some images I use from OE to OE-core. The
>>>> first issue I saw is there is no task-proper-tools in oe-core (where
>>>> oe-core means the set of layers created by the Angstrom setup scripts).
>>>>
>>> Philip,
>>>
>>> Have you looked at task-core-basic, it is supposed to be more of a
>>> desktop like set of tools, the idea being it's heavier weight than core,
>>> will move to supporting the non-graphical part of LSB.
>>>
>>> Another caveat for task-core-basic is that it's the largetest non-gplv3
>>> task that is used by core-image-basic.
>>>
>>> Does this task approach what you are looking for?
>>
>> It looks like a start, but I notice it brings in rpm. I'm not sure if I
>> want that. I would have thought that the package manager would be a
>> distro decision.
>>
> That's a bug that I would certainly take a patch for, unless rpm is
> required as part of LSB, that will need to be verified.
The ability to install RPM packages is required by the LSB. The LSB does not
require RPM however. (yes I know, odd requirement, but with things like alien
it's doable on debian systems.)
But yes, RPM is included to satisfy that requirement.
--Mark
> Sau!
>
>> Philip
>>
>>
>>>
>>> Sau!
>>>
>>>
>>>> Should I add task-proper-tools to meta-oe, or is there a better way to
>>>> add a full features set of tools to an image? Basically, the image is
>>>> more desktop like than embedded.
>>>>
>>>> Philip
>>>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>
>>>
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
> _______________________________________________
> 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:[~2011-10-04 22:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 19:58 Bringing an image from OE to OE-Core Philip Balister
2011-10-04 20:08 ` Saul Wold
2011-10-04 20:27 ` Philip Balister
2011-10-04 20:32 ` Saul Wold
2011-10-04 22:43 ` Mark Hatle [this message]
2011-10-05 14:14 ` Philip Balister
2011-10-05 14:47 ` Eric Bénard
2011-10-05 15:49 ` Mark Hatle
2011-10-05 16:20 ` Koen Kooi
2011-10-05 21:07 ` Philip Balister
2011-10-05 16:39 ` Eric Bénard
2011-10-05 19:35 ` Khem Raj
2011-10-05 20:03 ` Philip Balister
2011-10-05 20:18 ` Joshua Lock
2011-10-05 20:24 ` Khem Raj
2011-10-05 22:51 ` Saul Wold
2011-10-07 5:51 ` Frans Meulenbroeks
2011-10-04 20:15 ` Khem Raj
2011-10-04 20:27 ` 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=4E8B8C05.5050508@windriver.com \
--to=mark.hatle@windriver.com \
--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