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

[Koen Kooi]

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

Rod Whitby schreef:
> Stelios Koroneos wrote:
>> I am not sure how many of you are building multimachine distro's but the old
>> system was not a very good solution.
>> We are building a distro for a number of machines x86 arch (i486, i585,
>> i686), a number of powerpc targets  and recently mipsel and puttinng
>> everything in a giant ipk pool is not the best of solutions.
>>
>> As far as i can understand its a case where  single machine distro's made
>> use of this OE feature while multimachine distros had to look for other ways
>> (i.e post processing).
> 
> Perhaps when multimachine was added, the deploy ipk feed support should
> have been updated to continue to work, instead of later breaking single
> machine feed support.

Again, it didn't break anything that was *supported*. Rootfs generation continued to work.
However, rootfs_ipk.bbclass is *not* the place to put in feed management. That class is
supposed to build a rootfs from ipkgs, which it does by treating deploy/ipk/<arch> as
feeds. I can think of ways to do rootfs generation without Packages.* (e.g sqlite), and if
they prove to be faster and more robust I _will_ replace the old methods.

So my proposal:

Make a contrib/deploy-ipkg-feed.bb that basically does:

cd ${DEPLOY_DIR_IPK}
find */ -name  "*.ipk" -exec cp  '{}'  ./ \;
rm Packages*
ipkg-make-index -p Packages -l Packages.filelist -m .

and add the problems mentioned in other mails as comments.

This way people wanting a single feed get it with a simple 'bitbake -b
contrib/deploy-ipkg-feed.bb' without the impression it's officially supported in OE.

Does anyone have problems with this proposal?

regards,

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

iD8DBQFF5/XJMkyGM64RGpERAgtvAKChIZPrfuunIzm/pk7t83yim5zo0gCfQMli
OfEiT2MTSgKrxADF0pZhdw4=
=eWES
-----END PGP SIGNATURE-----