From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: USE flags mumbling
Date: Fri, 2 Jul 2010 08:22:04 +0200 [thread overview]
Message-ID: <20100702062204.GA9760@jama> (raw)
In-Reply-To: <4C2D153E.1040608@mentor.com>
On Thu, Jul 01, 2010 at 03:22:54PM -0700, Tom Rini wrote:
> I wonder, and I have to admit to having no real gentoo background
> here, how do they solve this problem? Did they invent their own
> package format and add another field that consists of use flags?
> That'd make some stuff a lot easier, but making deb/rpm get that
> mapping somehow seems hard at first.
They store all information about built packages in
/var/db/pkg/category/name/*
So they know which USE flags were ON and OFF when you built it, there is
also environment.bz2 where you can find which gcc version was used to
build it.
So it's easy to rebuild all installed packages if current systems
settings gives different USE flag sets then before (--newuse param) or
with small script I used to rebuild all remaining packages which weren't
rebuild after system gcc upgrade.
Lately (imho with new EAPI) they can also narrow dependencies not only
with requested version, but also with some USE flag ON or OFF.
And they have it much easier as they resolve it on target device, to
provide --newuse functionality in OE we would probably do PR bump of
all "changed" recipes.
So in the end it will be far from ideal if we try just to encode "our" USE
flags to ${PN}.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-07-02 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 16:24 USE flags mumbling Graeme Gregory
2010-07-01 16:50 ` Chris Larson
2010-07-01 17:00 ` Graeme Gregory
2010-07-01 20:53 ` Koen Kooi
2010-07-01 22:12 ` Chris Larson
2010-07-01 22:16 ` Tom Rini
2010-07-01 22:19 ` Chris Larson
2010-07-01 22:29 ` Phil Blundell
2010-07-01 22:33 ` Michael 'Mickey' Lauer
2010-07-01 22:39 ` Tom Rini
2010-07-02 6:01 ` Roman I Khimov
2010-07-02 6:52 ` Koen Kooi
2010-07-02 10:28 ` Richard Purdie
2010-07-01 22:22 ` Tom Rini
2010-07-02 6:10 ` Michael Lippautz
2010-07-02 6:22 ` Martin Jansa [this message]
2010-07-02 15:45 ` Tom Rini
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=20100702062204.GA9760@jama \
--to=martin.jansa@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.