All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: BBVERSIONS
Date: Tue, 23 Mar 2010 10:32:59 +0100	[thread overview]
Message-ID: <ac9c93b11003230232y2b556dc3t19813973d7c01b46@mail.gmail.com> (raw)
In-Reply-To: <b6ebd0a51003221526y7c47c57esd7bc14cc5e85f893@mail.gmail.com>

Chris, while this is a nice idea it conflicts with having checksums in
the recipe, as that makes the recipes unique.
Unless of course there is (or we create) a way to have multiple
checksums in a recipe and pick the one that is for the version we are
building.

Then again I feel it is in most cases better to move forward. E.g. for
your nano example: why would people want to build say nano 1.0.2 if
there is also a working 1.0.6 recipe (or even a 2.2.3 one or whatever
version it is at). I feel it is better to spent time to
fix/improve/add/repair the latest version than spend time fixing old
code.
(generally speaking that is)

Frans.



  reply	other threads:[~2010-03-23  9:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 22:26 BBVERSIONS Chris Larson
2010-03-23  9:32 ` Frans Meulenbroeks [this message]
2010-03-23  9:50   ` BBVERSIONS Holger Hans Peter Freyther
2010-03-23  9:58     ` BBVERSIONS Frans Meulenbroeks
2010-03-23 15:36     ` BBVERSIONS Chris Larson
2010-03-23 12:40   ` BBVERSIONS Michael Smith
2010-03-23 14:57   ` BBVERSIONS Chris Larson
2010-03-23  9:47 ` BBVERSIONS Martin Jansa
2010-03-23 15:41   ` BBVERSIONS Chris Larson
2010-03-23 15:57     ` BBVERSIONS Martin Jansa
2010-03-23 16:07       ` BBVERSIONS Chris Larson
2010-03-23 16:20         ` BBVERSIONS Martin Jansa
2010-03-23 20:45   ` BBVERSIONS Khem Raj
2010-03-23 22:19     ` BBVERSIONS Chris Larson
2010-03-23 15:42 ` BBVERSIONS Chris Larson

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=ac9c93b11003230232y2b556dc3t19813973d7c01b46@mail.gmail.com \
    --to=fransmeulenbroeks@gmail.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.