From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
Date: Wed, 19 Oct 2011 10:45:51 -0700 [thread overview]
Message-ID: <4E9F0CCF.3070404@intel.com> (raw)
In-Reply-To: <CAMKF1srj1OrgnSwihsVGDCVasAc6zTHRJkfAkjFOpM80mUFM9A@mail.gmail.com>
On 10/19/2011 10:00 AM, Khem Raj wrote:
> On Wed, Oct 19, 2011 at 9:57 AM, Saul Wold<saul.wold@intel.com> wrote:
>> On 10/19/2011 09:49 AM, Phil Blundell wrote:
>>>
>>> On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
>>>>
>>>> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
>>>>>
>>>>> It will be too many recipes to list on one line, shall I split the
>>>>> commit into multiple one for each recipe whose data is changed?
>>>>
>>>> Or per group, but saying "some toolchain recipes" is way too vague.
>>>
>>> Why do we have this distro tracking data in oe-core git anyway? I'm not
>>> entirely clear on what it's used by.
>>>
>> Phil:
>>
>> It's used by the tools that build http://packages.yoctoproject.org and to
>> help recipe manage maintainer-ship and track what needs updating.
>
> This could be managed via meta-data in packages I believe all that
> information is there.
>
Khem,
I am not quite following, are you suggesting incorporating the
distro_tracking_fields info into the final packages (this word is
overloaded sometimes), or adding it the recipe bb files?
If adding it to the recipe bb files, this was discussed and deemed
inappropriate, as it's too dynamic and would clutter the recipe.
Sau!
>>
>> Many upstreams we can't track if updates are required automagically, so we
>> need a place to record when the last manual check was, also possible reasons
>> why we should not update to newer versions, ...
>>
>> Sau!
>>
>>
>>> p.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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-19 17:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 8:28 [CONSOLIDATED PULL 00/16] Various Updates Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 01/16] poky: fix broken ubifs link in deploy folder Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 02/16] bluez4: Add glib-2.0 to DEPENDS Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 03/16] gcc-4.6: Upgrade SRCREV to latest FSF 4.6 branch Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 04/16] gcc-4.6: Backport PR46934 fix Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 05/16] ghostscript: Disable parallel make due to install issues Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 06/16] src_distribute.bbclass, src_distribute_local.bbclass: mostly rewritten Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 07/16] ghostscript: renamed x86_64 to x86-64 for patch to work Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 08/16] insane.bbclass: print full path on invalid LICENSE_FILES_CHKSUM Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 09/16] x86 tune files: set baselib for x32 tune as libx32 Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 10/16] gmp: also generate the libgmpcxx library Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 11/16] python-scons: upgrade from 2.0.1 to 2.1.0 Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 12/16] python-dbus: upgrade from 0.83.2 to 0.84.0 Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 13/16] libxml-parser-perl: upgrade from 2.40 to 2.41 Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes Saul Wold
2011-10-19 8:30 ` Koen Kooi
2011-10-19 15:49 ` Kamble, Nitin A
2011-10-19 15:52 ` Koen Kooi
2011-10-19 16:24 ` Kamble, Nitin A
2011-10-19 16:37 ` Koen Kooi
2011-10-19 16:49 ` Phil Blundell
2011-10-19 16:57 ` Saul Wold
2011-10-19 17:00 ` Khem Raj
2011-10-19 17:45 ` Saul Wold [this message]
2011-10-19 18:30 ` Khem Raj
2011-10-19 19:00 ` Otavio Salvador
2011-10-19 23:33 ` Saul Wold
2011-10-20 14:25 ` Richard Purdie
2011-10-20 14:36 ` Martin Jansa
2011-10-20 14:48 ` Koen Kooi
2011-10-20 15:55 ` Richard Purdie
2011-10-20 16:24 ` Koen Kooi
2011-10-20 17:38 ` Joshua Lock
2011-10-20 21:28 ` Saul Wold
2011-10-20 16:18 ` Khem Raj
2011-10-20 16:02 ` Eric Bénard
2011-10-19 8:28 ` [CONSOLIDATED PULL 15/16] gst-plugins-good: update to 0.10.30 Saul Wold
2011-10-19 8:28 ` [CONSOLIDATED PULL 16/16] tzdata: updated SRC_URI and update to 2011k 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=4E9F0CCF.3070404@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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