All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eliyahu Skoczylas" <EliSko@FastMail.fm>
To: "Developers@OE.net" <openembedded-devel@lists.openembedded.org>
Subject: Re: busybox recipe isappearances
Date: Thu, 23 Oct 2008 12:12:07 +0200	[thread overview]
Message-ID: <1224756727.28423.1280823321@webmail.messagingengine.com> (raw)
In-Reply-To: <4900464A.9090009@kernelconcepts.de>

On Thu, 23 Oct 2008 11:39:22 +0200, "Florian Boor"
<florian.boor@kernelconcepts.de> said:
> Hi,
> 
> Phil Blundell schrieb:
> > It's long been my view that we should just add newer ones and leave the
> > old ones alone.  There's really no reason to delete old recipes and,
> > even if you check for PREFERRED_VERSIONs in the git tree, there is no
> > real way to know who else might be relying on the version you are about
> > to delete. 
> 
> I share this opinion. Since we do not know what people are doing with OE
> there
> is no way to find out if a recipe is used or not. In fact I can imagine a
> lot of
> situations in which you might want to use an older recipe.
> 
> Why do we delete old recipes? We do not do this with old software
> releases.

I think that a simple policy of retaining, say, the latest 3 or 4
recipes for the current version of a package, and the last 2 for the 2
earlier software versions, might make people's lives easier and also not
"clutter up" the directories with dozens of out-of-date / non-working
versions.  It shouldn't be hard to automate a policy like that, either.

-    Eliyahu
--
Eliyahu Skoczylas    +972 (54) 214-1505
If <EliSko@Eli-Sko.com> bounces, please use <EliSko@FastMail.fm>, instead.




  reply	other threads:[~2008-10-23 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19 16:11 busybox recipe isappearances Koen Kooi
2008-10-19 16:47 ` Michael 'Mickey' Lauer
2008-10-19 17:46   ` Phil Blundell
2008-10-19 18:08     ` Richard Purdie
2008-10-19 22:02     ` Michael 'Mickey' Lauer
2008-10-20  7:47       ` Phil Blundell
2008-10-20 11:22         ` Thomas Kunze
2008-10-23  9:39     ` Florian Boor
2008-10-23 10:12       ` Eliyahu Skoczylas [this message]
2008-10-27 13:26       ` Michael 'Mickey' Lauer

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=1224756727.28423.1280823321@webmail.messagingengine.com \
    --to=elisko@fastmail.fm \
    --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.