Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Upgrade chrpath and libevent
Date: Thu, 29 Dec 2011 22:06:59 +0000	[thread overview]
Message-ID: <3173273.Kh9LKRsTpP@helios> (raw)
In-Reply-To: <4EFCD0B5.6080702@intel.com>

On Thursday 29 December 2011 15:42:29 Scott Garman wrote:
> On 12/29/2011 10:28 AM, Paul Eggleton wrote:
> > On Thursday 29 December 2011 10:05:52 Scott Garman wrote:
> >> On 12/28/2011 01:37 PM, Saul Wold wrote:
> >>> This will probably require a PR bump for nfs-utils then.
> >> 
> >> Are you sure? I thought this was handled automatically as long as the
> >> recipe in question includes the build dependency in DEPENDS, as
> >> nfs-utils does for libevent.
> > 
> > Yes, if you want nfs-utils to be rebuilt you'll need to bump its PR.
> > When we eventually move over to the PR server that won't be necessary.
> 
> Wow, this is really surprising to me. In all of the recipe upgrades I've
> ever previously done, I've *never* bumped the PR for all other recipes
> that list it in DEPENDS. Is this a new procedure we'll have to adopt for
> the core metadata team?

It's a judgement call. If there is an ABI being provided which has changed 
incompatibly then you definitely should bump PRs of those recipes that depend 
on it. Thinking about it, it probably wouldn't be too hard to detect when the 
ABI has been broken if we wanted to put some safeguards in place.

I don't think we've been vigilant about this in the past but because people 
try not to change ABIs we get away with it most of the time. Not sure if it 
warrants any change in procedure but extra care at least can't hurt.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-12-29 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 17:31 [PATCH 0/2] Upgrade chrpath and libevent Scott Garman
2011-12-23 17:31 ` [PATCH 1/2] chrpath: upgrade to 0.14 Scott Garman
2011-12-23 17:31 ` [PATCH 2/2] libevent: upgrade to 2.0.16 Scott Garman
2011-12-23 17:42 ` [PATCH 0/2] Upgrade chrpath and libevent Scott Garman
2011-12-26 21:12   ` Scott Garman
2011-12-28 18:37     ` Saul Wold
2011-12-29 15:05       ` Scott Garman
2011-12-29 15:28         ` Paul Eggleton
2011-12-29 20:42           ` Scott Garman
2011-12-29 22:06             ` Paul Eggleton [this message]
2012-01-04  0:02 ` Saul Wold

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=3173273.Kh9LKRsTpP@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=scott.a.garman@intel.com \
    /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