From: Phil Blundell <philb@gnu.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] meta: remove redundant _FOR_BUILD variables
Date: Sat, 10 Nov 2012 11:11:38 +0000 [thread overview]
Message-ID: <1352545898.6869.103.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAP9ODKpa0gkf5ZQGVemLYRNKVKA4cWbV4v1E_SZwAs9RuMd61A@mail.gmail.com>
On Fri, 2012-11-09 at 21:23 -0200, Otavio Salvador wrote:
> If it rebuilds it might get a different binary package and for
> preserve the upgrade path PR bumps are need, aren't they?
Binary upgrade paths have always been a DISTRO issue. If you want to
bump PR on everything in your distro config then you certainly can do
that, though from the point of view of an end-user I don't think that
performing a phony "upgrade" of every autotools-using package without
any functional change would necessarily be a desirable thing.
The whole PR-bumping thing is just a massive pain in the backside and,
now that all the metadata is hashed into the signature files anyway, I
think we should consider just ditching PR from oe-core altogether.
Distros that want to go on using PR can do so, either by maintaining it
manually or by using some sort of automated PR server. Distros that
don't use binary feeds and/or support online upgrades will generally
have less of a requirement for PR and might prefer just to do without it
altogether.
p.
next prev parent reply other threads:[~2012-11-10 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 10:09 [PATCH 0/2] Consolidate _FOR_BUILD variables Ross Burton
2012-11-09 10:09 ` [PATCH 1/2] autotools: set _FOR_BUILD variables here Ross Burton
2012-11-09 10:09 ` [PATCH 2/2] meta: remove redundant _FOR_BUILD variables Ross Burton
2012-11-09 22:32 ` Otavio Salvador
2012-11-09 22:57 ` Richard Purdie
2012-11-09 23:23 ` Otavio Salvador
2012-11-10 10:05 ` Richard Purdie
2012-11-10 11:11 ` Phil Blundell [this message]
2012-11-10 11:20 ` Tomas Frydrych
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=1352545898.6869.103.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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