From: Mark Hatle <mark.hatle@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] Misc changes relating to toolchain and image gen
Date: Tue, 12 Nov 2013 21:42:53 -0600 [thread overview]
Message-ID: <5282F53D.8050001@windriver.com> (raw)
In-Reply-To: <5282DD70.3040705@windriver.com>
On 11/12/13, 8:01 PM, Mark Hatle wrote:
> On 11/12/13, 7:33 PM, Otavio Salvador wrote:
>> On Tue, Nov 12, 2013 at 11:23 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> A few misc fixes relating to toolchain and image generation.
>>>
>>> The first two in the set simply updated gcc to remove the -symlinks package
>>> in favor of update-alternatives.
>>>
>>> The next fixes an issue w/ the previous binutils patch and upgrades.
>>>
>>> Next 2 update packagegroups to make revise and use the
>>> packagegroup-core-buildessentials.
>>>
>>> The final patch fixes an issue w/ the image generatation. If the
>>> IMAGE_INSTALL contains a dependency instead of a package name, the system
>>> was not able to translate it into a package. This now works properly.
>>>
>>> Note, there is a case where an unresolvable set could be determined (rare,
>>> but it is possible), in this case the user would need to add whatever is
>>> required to fix it to the IMAGE_INSTALL. (This could happen when 2 or more
>>> conflicting packages all have the same provide, but none of them are in
>>> the IMAGE_INSTALL line. The system will attempt to determine which to
>>> use, by checking if any of them are already in the IMAGE_INSTALL -- otherwise
>>> it chooses the first entry. If something else implied by a packagegroup
>>> chooses a different version, a conflict would be generated.)
>>
>> Which package backends has been tested with those changes?
>>
>
> 6/6 only affects RPM. So only RPM back end.
>
> The other changes are generic and follow the existing models. However, I only
> tested the RPM backend.
BTW I just verified that the 1-5/6 work properly with an opkg backend as well.
--Mark
> (Note v2 of 5/6 and 6/6 has been sent. I accidentally sent a version prior to
> two minor revisions.)
>
> --Mark
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-11-13 3:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 1:23 [PATCH 0/6] Misc changes relating to toolchain and image gen Mark Hatle
2013-11-13 1:23 ` [PATCH 1/6] gcc: Use alternatives for the *-symlinks packages Mark Hatle
2013-11-13 2:24 ` Otavio Salvador
2013-11-13 2:27 ` Mark Hatle
2013-11-13 2:28 ` Otavio Salvador
2013-11-13 1:23 ` [PATCH 2/6] gcc: Drop *-symlinks Mark Hatle
2013-11-13 1:23 ` [PATCH 3/6] binutils: Ensure old -symlinks packages get removed Mark Hatle
2013-11-13 8:12 ` Martin Jansa
2013-11-13 11:14 ` Phil Blundell
2013-11-13 13:39 ` Mark Hatle
2013-11-13 13:44 ` Phil Blundell
2013-11-13 1:23 ` [PATCH 4/6] packagegroups: Remove toolchain *-symlinks packages Mark Hatle
2013-11-13 1:23 ` [PATCH 5/6] packagegroup-self-hosted: Use packagegroup-core-buildessentials Mark Hatle
2013-11-13 1:23 ` [PATCH 6/6] package_rpm: Allow translation of requirement to package name Mark Hatle
2013-11-13 1:33 ` [PATCH 0/6] Misc changes relating to toolchain and image gen Otavio Salvador
2013-11-13 2:01 ` Mark Hatle
2013-11-13 3:42 ` Mark Hatle [this message]
2013-11-13 1:59 ` [PATCH 5/6 v2] packagegroup-self-hosted: Use packagegroup-core-buildessential Mark Hatle
2013-11-13 1:59 ` [PATCH 6/6 v2] package_rpm: Allow translation of requirement to package name Mark Hatle
2013-11-13 10:33 ` Paul Eggleton
2013-11-13 12:31 ` Otavio Salvador
2013-11-13 13:12 ` Mark Hatle
2013-11-15 14:02 ` Richard Purdie
2013-11-15 17:15 ` Mark Hatle
2013-11-13 14:19 ` [PATCH 2/6 v3] gcc: Drop *-symlinks Mark Hatle
2013-11-13 14:19 ` [PATCH 3/6 v3] binutils: Ensure old -symlinks packages get removed Mark Hatle
2013-11-19 0:40 ` [PATCH 0/6] Misc changes relating to toolchain and image gen Saul Wold
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=5282F53D.8050001@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@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 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.