[oe] [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools

[Koen Kooi]

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

Richard Purdie schreef:
> On Sun, 2007-03-04 at 09:43 +0100, Koen Kooi wrote:

>> So it always required an extra command (either 'bitbake <foo>-image' or 'bitbake
>> package-index'), since the index wasn't refreshed automagically after you built a package.
> 
> Nobody has a problem with that.

People did seem to have problems with that, citing 'needless post processing' when I said
you need to run one (1) command to get a feed! But we'll from now on assume people have no
problems with it.

> OE is not just about image generation!

I didn't say that, I meant that people wanting a Packages.* in deploy/ipk _most likely_
have more packages there than <foo>-image will generate and hence move out of do_rootfs
territory.
FWIW, image generation is ~5% of what I use OE for.


> I accept there is a fine line between this and supporting feed
> generation from OE. The thing is people have been happily using that
> directory as a feed, not for users but for development work. I don't
> think its fair to break that when we don't need to.

It didn't break, it _moved_, the subdirectories can still be used as development feeds.
Instead of saying

echo 'src/gz devfeed http://buildbox/tmp/deploy/ipk' > /etc/ipkg/devfeed.conf

you will now say

echo 'src/gz devfeed1 http://buildbox/tmp/deploy/ipk/ppc603e' > /etc/ipkg/devfeed1.conf
echo 'src/gz devfeed2 http://buildbox/tmp/deploy/ipk/efika' > /etc/ipkg/devfeed2.conf

Right? Or did the cset *really* break that as people keep claiming?

Assuming the above didn't break, what about this:

'bitbake package-index' will generate a deploy/bogofeed, everything else stays as it is now.


regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF6q4TMkyGM64RGpERAgN/AJ9fb59es7p6p+rJ4Uhwsn+2QUJ6QwCePf/f
Sk9wVjfSY4bvmVEs0jfAeOo=
=wBAr
-----END PGP SIGNATURE-----