All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of may
Date: Wed, 19 May 2010 18:23:56 -0700	[thread overview]
Message-ID: <4BF48F2C.8010908@mentor.com> (raw)
In-Reply-To: <20100520003151.GA26630@gmail.com>

Khem Raj wrote:
> On (20/05/10 05:16), Holger Freyther wrote:
[snip]
>> Removing old versions
>> =====================
>> The TSC looked into the topic of when to remove versions.
>>
>>
>> The TSC thinks there can not be a general rule of when to delete
>> a package. The TSC believes that in some cases a package should
>> never be deleted, e.g. with GCC/GLIBC to target a specific device
>> or distribution. For a series of major releases it seems plausible
>> to only keep the latest minor release of each release series around
>> given that the quality should increase with each minor release but
>> a removal of a minor release should not be done if there is a
>> PREFERRED_VERSION set. The TSC believes that 24 months can be a good
>> time to remove old major releases but it is certainly not the only
>> criteria for a removal.
> 
> gcc makes minor releases and in general they are bug fix only releases.
> like kernel.
> 
> I would propose that OE count such packages with major release only.
> e.g. gcc 4.4 (indicated 4.4.x) 4.5 and so on. This will simplify the
> maintenance and reduce duplication, with one downside that if some DISTRO does not need a 
> bug fix that was say done in 4.4.4 and is currently using 4.4.3 as
> preferred cross compiler. Although chances of such cases will be low.

In general, I think this will be OK.  But the compat with __ external 
distro cases (both say old compat things or as just an example, Android 
1.x uses gcc 4.2.1 iirc as the libgcc exception was still WIP for GPLv3) 
are the exception.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-05-20  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 21:16 TSC Meetings for the meeting of may Holger Freyther
2010-05-20  0:31 ` Khem Raj
2010-05-20  1:23   ` Tom Rini [this message]
2010-05-20  2:42     ` 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=4BF48F2C.8010908@mentor.com \
    --to=tom_rini@mentor.com \
    --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.