All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Why PREFERRED_VERSION setting of <distro>.conf overrules local.conf setting ?
Date: Tue, 10 Aug 2010 22:50:31 +0200	[thread overview]
Message-ID: <i3se2n$gj7$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimbjUYY22nf59gPAw-Xm05mMLNdDA61Ydc63DFs@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10-08-10 01:15, Graham Gower wrote:
> On 10 August 2010 04:31, Frans Meulenbroeks <fransmeulenbroeks@gmail.com> wrote:
>> 2010/8/9 Chris Larson <clarson@kergoth.com>:
>>> On Mon, Aug 9, 2010 at 6:26 AM, Hauser, Wolfgang (external) <
>>> Wolfgang.Hauser.external@eads.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I want to change some used versions of packages, so I added a
>>>> PREFERRED_VERSION_<package>="xxx" for the packages I want to have a
>>>> special(newer) version to be used.
>>>>
>>>> But e. g. for busybox the version defined in the used <distro>.conf is
>>>> used instead of my setting in local.conf.
>>>>
>>>> Should local.conf not overrule <distro/machine>.conf ??
>>>
>>>
>>> Conceptually, local should override everything, as it's the "most specific"
>>> information available, but from a technical standpoint, we can't parse the
>>> machine and distro configs until local.conf is parsed, as that's usually
>>> where the MACHINE and DISTRO are set.  You can use a 'local' override to get
>>> around it, or you can ask the distro/machine maintainer to use ?=
>>> assignments (set only if unset).
>>>
>>> PREFERRED_VERSION_<package>_local = "xxx" is how you use the override.
>>
>> The real solution woud be to either temporary store the
>> PREFERRED_VERSION and apply it later on.
>> Alternately we could parse local.conf twice, the first time ignoring
>> the PREFERRED lines, and the 2nd time only looking at these.
>> Yet another solution could be to split local.conf into two pieces, one
>> with settings like MACHINE and DISTRO, the other one with the
>> overrides.
> 
> Wouldn't it be far simpler to fix the distro conf file(s)? E.g. apply
> something like this:
> s/^PREFERRED_VERSION_\([a-z]*\) =/PREFERRED_VERSION_\1 ?=/

What's the point of setting a preferred version at all if you make it a
weak assignment?
The distro nearly always knows better and if you want to use a different
version, sending a patch to change that version for review isn't exactly
rocket science.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMYbuWMkyGM64RGpERArMuAKCmQ+N+ZFpZv9/s24LYacKaPMLUJwCfaUGs
JSGK2aDWhxS1Ii6uVkUGoIQ=
=jBaa
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-08-10 20:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 13:26 Why PREFERRED_VERSION setting of <distro>.conf overrules local.conf setting ? Hauser, Wolfgang (external)
2010-08-09 14:22 ` Chris Larson
2010-08-09 19:01   ` Frans Meulenbroeks
2010-08-09 23:15     ` Graham Gower
2010-08-10  7:00       ` Frans Meulenbroeks
2010-08-11  3:59         ` Mike Westerhof
2010-08-10 20:50       ` Koen Kooi [this message]
2010-08-10 20:56         ` Chris Larson
2010-08-10 23:44           ` Graham Gower
2010-08-11  1:42             ` Denys Dmytriyenko
2010-08-11  2:43               ` Graham Gower
2010-08-11  3:10                 ` Denys Dmytriyenko
2010-08-11  5:16           ` Khem Raj
2010-08-11  6:08             ` Frans Meulenbroeks
2010-08-11  6:20               ` Martin Jansa
2010-08-11  7:53                 ` Hauser, Wolfgang (external)
2010-08-11  8:28                   ` Khem Raj
2010-08-11  9:50                     ` Why PREFERRED_VERSION setting of <distro>.conf overruleslocal.conf " Hauser, Wolfgang (external)

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='i3se2n$gj7$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.