Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] Koen Kooi : angstrom 2009.X: bump automake-native to 1.10. 2 since some idiot deleted 1.10
Date: Wed, 04 Mar 2009 11:13:30 +0100	[thread overview]
Message-ID: <golk8b$52t$1@ger.gmane.org> (raw)
In-Reply-To: <49AE5117.5020806@gefanuc.com>

On 04-03-09 10:59, Martyn Welch wrote:
> Michael 'Mickey' Lauer wrote:
>> Am Dienstag, den 03.03.2009, 17:38 -0500 schrieb Philip Balister:
>>> Michael 'Mickey' Lauer wrote:
>>>> Am Dienstag, den 03.03.2009, 21:49 +0100 schrieb GIT User account:
>>>>> Module: openembedded.git
>>>>> Branch: org.openembedded.dev
>>>>> Commit: eee859a9c348871d6d644ece76bc57b151cc80e8
>>>>> URL:
>>>>> http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=eee859a9c348871d6d644ece76bc57b151cc80e8
>>>>>
>>>>>
>>>>> Author: Koen Kooi <koen@openembedded.org>
>>>>> Date: Tue Mar 3 21:47:57 2009 +0100
>>>>>
>>>>> angstrom 2009.X: bump automake-native to 1.10.2 since some idiot
>>>>> deleted 1.10
>>>> Ah, are we in that mood again? Take more pills.
>>> We need to have a serious discussion about deleting recipes. I know
>>> the deletion of python 2.5 will force me to address the 2.5->2.6
>>> upgrade in gnuradio before the upstream developers are ready.
>>>
>>> We need a way to remove recipes, but doing it as part of adding a new
>>> recipe is causing problems for OE users.
>>
>> Yes, we need to have a serious discussion about lots of things
>> surrounding the OpenEmbedded project, before the popularity kills the
>> project. Judging from the amount of interest though, I don't see that
>> happening -- neither short term nor long term.
>>
>
> Ok, so if a serious discussion is out of the question, lets just have a
> normal discussion.
>
> I see this issue to be partially related to the on going discussions
> regarding submissions. I assume that the "Commit_Policy"[1] on the wiki
> is either unofficial, out-of-date or optional as it states:
>
> * Changes to core toolchain components need review (gcc, binutils,
> libtool, pkgconfig, automake, autoconf etc.)
>
> Where:
>
> "Review" is defined as posting it on the mailing lists and getting
> positive agreement from two or more core developers.
> Now a quick check of my OpenEmbedded mail folder doesn't chuck up any
> messages with automake in the title that have a patch with this commit.
> Maybe I'm looking on the wrong mailing list.

I haven't seen anything like that either, and upgrading automake *did* 
break, since a lot of apps now do 'install -s' which calls host strip :(
This is exactly why we did extensive testing the last time we touched 
automake.

regards,

Koen




  reply	other threads:[~2009-03-04 10:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090303204954.CCB9CE8008@amethyst.openembedded.net>
2009-03-03 22:25 ` [oe-commits] Koen Kooi : angstrom 2009.X: bump automake-native to 1.10. 2 since some idiot deleted 1.10 Michael 'Mickey' Lauer
2009-03-03 22:38   ` Philip Balister
2009-03-03 22:56     ` Michael 'Mickey' Lauer
2009-03-04  9:59       ` Martyn Welch
2009-03-04 10:13         ` Koen Kooi [this message]
2009-03-04 14:18           ` Martyn Welch
2009-03-04 15:43             ` Philip Balister
2009-03-04 10:21         ` Michael 'Mickey' Lauer
2009-03-04 10:54           ` Koen Kooi
2009-03-04 11:23             ` Michael 'Mickey' Lauer
2009-03-04 11:41               ` Koen Kooi
2009-03-04 15:06                 ` GNUtoo
2009-03-04 11:42               ` Martyn Welch
2009-03-04 15:42                 ` Philip Balister
2009-03-05 15:32               ` Otavio Salvador
2009-03-05 15:30             ` Otavio Salvador
2009-03-04  7:49     ` Frans Meulenbroeks
2009-03-04  7:55     ` Koen Kooi
2009-03-04  7:56     ` Stanislav Brabec

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='golk8b$52t$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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