All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch to fix libstdc++ problem, was Re: Images no longer automatically include libstdc++6
Date: Sun, 12 Sep 2010 09:04:27 -0400	[thread overview]
Message-ID: <4C8CCFDB.5000103@balister.org> (raw)
In-Reply-To: <AANLkTikqWixYAegBhiVamN2GpG_jMZCpRH=a-9NunbF7@mail.gmail.com>

On 09/12/2010 08:49 AM, Frans Meulenbroeks wrote:
> 2010/9/12 Philip Balister<philip@balister.org>:
>
>> If the DISTRO is not maintained, maybe it should be cleaned up and left
>> around to confuse people who think it should work well.
>>
>
> Philip,
>
> I hope you wanted to say "...cleaned up and NOT left around..."
> Otherwise it does not really make sense to me.

I did. I am not functioning on a full load of coffee.

Seriously, some people may be attached to those distro's. However, if 
they are not using OISTRO_PR to force rebuilds may be due to their use 
case being different from say Angstrom. DISTRO_PR is useful for people 
maintained feeds for end users. Some of the DISTRO's without it, may 
just build images from clean builds as needed, so they don't really need 
it, and won't need the PR bump being discussed.

Philip

>
> BTW: I already tried to identify distro maintainers and unmaintained
> distros. See [1]
> I still feel it is a good plan to either remove unmaintaned distros,
> or move them (and the files that are specific to those distros) to an
> unmaintained directory.
> However it was even impossible to create consensus to remove files in
> distro/include that were not used by any distro (and most likely not
> maintained either) See [2]
>
> [1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-August/022698.html
> [2] http://thread.gmane.org/gmane.comp.handhelds.openembedded/35427/focus=35946
>
> Frans.
>
> PS: and if anyone would need it, it would still be availalble in git
> as well as in the stable/2009 branch. I can also imagine that we
> create a tag before actually cleaning up.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



  reply	other threads:[~2010-09-12 13:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 22:21 Images no longer automatically include libstdc++6 Steve Sakoman
2010-09-06 22:52 ` J. L. 
2010-09-07  5:54 ` Khem Raj
2010-09-07  8:20   ` J. L. 
2010-09-07 12:52   ` Koen Kooi
2010-09-07 16:18     ` Khem Raj
2010-09-07 19:03       ` Koen Kooi
2010-09-08  6:01         ` Frans Meulenbroeks
2010-09-08 14:09         ` pieterg
2010-09-08 14:33           ` Philip Balister
2010-09-11  1:29             ` Dallas Foley
2010-09-11  7:09               ` Koen Kooi
2010-09-11  7:46                 ` patch to fix libstdc++ problem, was " Koen Kooi
2010-09-12  8:34                   ` Frans Meulenbroeks
2010-09-12  9:11                     ` Koen Kooi
2010-09-12 11:27                       ` Frans Meulenbroeks
2010-09-12 11:48                         ` Koen Kooi
2010-09-12 12:11                           ` Frans Meulenbroeks
2010-09-12 12:27                         ` Philip Balister
2010-09-12 12:49                           ` Frans Meulenbroeks
2010-09-12 13:04                             ` Philip Balister [this message]
2010-09-12 13:23                               ` Frans Meulenbroeks
2010-09-12 18:52                   ` Koen Kooi
2010-09-13  6:23                     ` Frans Meulenbroeks
2010-09-13  7:22                       ` Graham Gower
2010-09-12 21:08                   ` pieterg
2010-09-12 23:56                     ` dfoley
2010-09-13  6:01                   ` Khem Raj

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=4C8CCFDB.5000103@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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 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.