From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] sane-providers.inc with default providers for all distributions
Date: Fri, 04 Dec 2009 11:00:17 +0100 [thread overview]
Message-ID: <hfamji$7nr$1@ger.gmane.org> (raw)
In-Reply-To: <20091204090048.GA3233@jama>
On 04-12-09 10:00, Martin Jansa wrote:
> I would like to create new file conf/distro/include/sane-providers.inc
> where we could store all default providers.
If it's the same for everyone, can't it be put in bitbake.conf? I'm
growing a bit tired of mandatory sane-* files to include.
regards,
Koen
> Every distro should include this file and probably should drop own
> PREFERRED_PROVIDERS if preferring same provider as sane-providers.inc.
>
> I already prepared something, but not sure if its worth finishing. So I
> need your opinion.
>
> With this file it would be easier to add PROVIDES to new recipe while
> forcing old provider in sane-providers for all other distributions
> (something like what happen with fso-apm in shr).
>
> Maybe it will be nice to have all options in comment above the default
> provider.
>
> I would use weak assignments in this file, but it means that this file
> needs to be included after all distro prefered providers, because distro
> config use weak assignments too (and also other includes like eglibc.inc).
>
> As opkg have patch from cworth now I would add
> PROVIDERS=update-alternatives to opkg and change preferred u-a provider
> to opkg (removing 2 u-a scripts on target).
>
> This process seems a bit error prone to me, so I can prepare patch for
> shr and angstrom where I can test with rebuild that "nothing" changed.
> For other distributions it would be nice to include sane-providers by
> distro maintainers.
>
> Can I go ahead and send patches for this or do you see some dead-end as
> with SRCPV? :).
>
> Regards,
>
next prev parent reply other threads:[~2009-12-04 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 9:00 [RFC] sane-providers.inc with default providers for all distributions Martin Jansa
2009-12-04 10:00 ` Koen Kooi [this message]
2009-12-04 10:17 ` Otavio Salvador
2009-12-06 21:13 ` Martin Jansa
2009-12-06 21:13 ` [PATCH 1/6] bitbake.conf: create compatibility-providers.conf from micro, minimal, angstrom, shr preferred providers Martin Jansa
2009-12-06 21:13 ` [PATCH 2/6] micro.conf: remove preferred providers as the same are defined in compatibility-providers.conf Martin Jansa
2009-12-06 21:13 ` [PATCH 3/6] minimal.conf: " Martin Jansa
2009-12-06 21:13 ` [PATCH 4/6] angstrom-2008.1.conf: remove preferred providers set already " Martin Jansa
2009-12-06 21:13 ` [PATCH 5/6] shr.conf: " Martin Jansa
2009-12-06 21:13 ` [PATCH 6/6] opkg: add provides for update-alternatives and set opkg as default u-a provider in sane-feed-ipk Martin Jansa
2009-12-06 22:01 ` [PATCH 1/6] bitbake.conf: create compatibility-providers.conf from micro, minimal, angstrom, shr preferred providers Otavio Salvador
2009-12-06 22:07 ` [PATCH] compatibility-providers.conf: comment out 2nd atd provider Martin Jansa
2009-12-06 23:45 ` [PATCH 1/6] bitbake.conf: create compatibility-providers.conf from micro, minimal, angstrom, shr preferred providers Koen Kooi
2009-12-07 6:16 ` Martin Jansa
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='hfamji$7nr$1@ger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox