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: [RFC] Remove older freetype versions
Date: Tue, 12 Oct 2010 10:03:17 -0700	[thread overview]
Message-ID: <4CB494D5.3010900@mentor.com> (raw)
In-Reply-To: <4CB490CD.50500@balister.org>

Philip Balister wrote:
> On 10/12/2010 12:41 PM, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 12-10-10 18:26, Tom Rini wrote:
>>> Hey all,
>>>
>>> I'd like to remove all versions of freetype before 2.4.3.  The only dist
>>> which is pinning freetype currently does so via
>>> conf/distro/include/preferred-opie-versions.inc and that pins to a
>>> non-existent version (it's using OPIE_VERSION which seems wrong).  All
>>> of the previous versions have various security issues, including
>>> remotely exploitable ones.  Only the very oldest version we have as a
>>> D_P -1 so everyone was using 2.3.12 and will be going up to 2.4.3
>>> (libraries are compat).
>>
>> Speaking of freetype, the bytecode patent expired, so we can turn that
>> on and get nicer text :)
>>
>> And removing older freetypes is a good idea
> 
> I'd like to point people at openwmbedded/removal.txt. This would be a 
> good place to schedule things for deletion. As in I added a new version 
> and made it active, but do not want to delete the older version for a 
> couple of months just in case something crops up. So leave a note in 
> removal.txt to look are removing a recipe on a certain date.

In general, good idea.  But we've been doing things a lot quicker more 
recently.  And I'd like to not wait for a long time for security related 
items.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-10-12 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 16:26 [RFC] Remove older freetype versions Tom Rini
2010-10-12 16:41 ` Koen Kooi
2010-10-12 16:46   ` Philip Balister
2010-10-12 17:03     ` Tom Rini [this message]
2010-10-12 20:59       ` Frans Meulenbroeks
2010-10-12 17:17 ` Martin Jansa

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=4CB494D5.3010900@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.