From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: adding an updated package, and when it's safe to do so?
Date: Fri, 20 Nov 2009 10:13:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911201012020.21364@localhost> (raw)
In-Reply-To: <1258729646.8426.2.camel@conroy-linux>
On Fri, 20 Nov 2009, Chris Conroy wrote:
> On Thu, 2009-11-19 at 20:54 -0500, Robert P. J. Day wrote:
> > a couple silly questions while i prep a guile package update.
> >
> > 1) if a newer package is added under recipes, i'm assuming that
> > it's the newest version of the package that will be used for a
> > build, unless a PREFERRED_VERSION directive is used, correct?
> >
> > 2) at what point can i start to add that new package info so that
> > a current build doesn't pick it up? once all the .bb files are
> > parsed and the package builds are underway, is that it for any
> > further consultation of the .bb files?
>
> I'm not sure if I'm understanding your problem correctly, but to me
> it sounds like you just want to set DEFAULT_PREFERENCE="-1" in the
> recipe you're concerned about.
not really, i was simply asking what *would* happen upon the
addition of a newer version of a package, that's all.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-11-20 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 1:54 adding an updated package, and when it's safe to do so? Robert P. J. Day
2009-11-20 15:07 ` Chris Conroy
2009-11-20 15:13 ` Robert P. J. Day [this message]
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=alpine.LFD.2.00.0911201012020.21364@localhost \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox