From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: RFC: DISTRO_FEED_CONFIGS
Date: Mon, 24 Dec 2007 08:58:38 +0100 [thread overview]
Message-ID: <476F66AE.40601@student.utwente.nl> (raw)
In-Reply-To: <476F07C6.7010308@whitby.id.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rod Whitby schreef:
> I would like to propose a new standard OE variable called
> DISTRO_FEED_CONFIGS which is a list of packages to be installed in a
> rootfs to enable the corresponding DISTRO_PACKAGE_MANAGER to actually
> access the feeds associated with the distro. A distro which did not
> have feed config packages could leave it as the default empty string and
> remain unchanged in the face of this RFC.
>
> This variable would be set in the respective distro.conf, along with
> DISTRO_PACKAGE_MANAGER. It would initially be used in base-image.bb
> (see that file for an example of use), and then elsewhere as desired.
>
> For example, in Angstrom, it would replace the existing
> ANGSTROM_FEED_CONFIGS variable.
+1 from me.
As a side note: this won't touch how the FEED_URIs for static feeds are
used, but will only affect distros that want to put them under
package-management.
regards,
Koen
- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHb2auMkyGM64RGpERAvyQAJ4tFxwOU5hvhO6RuvUNhTZywXDQBwCeLiDr
IxBBYAK2LRWcG0Y1Ief8wGA=
=CVj6
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-12-24 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 1:13 RFC: DISTRO_FEED_CONFIGS Rod Whitby
2007-12-24 7:58 ` Koen Kooi [this message]
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=476F66AE.40601@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.