[Angstrom-devel] [RFC] Packaged-staging feed project
fransmeulenbroeks at gmail.com
Thu Feb 11 11:08:57 CET 2010
2010/2/11 Koen Kooi <k.kooi at student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Now that packaged-staging seems to be working again, I think it's time
There are some issues left.
one is that sometimes one gets messages about unknown architecture.
This msg is given by opkg. Haven't really found the cause yet and have
hardly time to dig into it in the upcoming days.
The other is that some packages are mentioned as invalid. This happens
for native packages that are generated with the regular recipes and
Tom Rini seemed to have an idea about the latter, but haven't spoken
to him since.
> we come up with some infrastructure to leverage it properly for angstrom.
> I was thinking about a workflow like this:
> * build console-image for your favourite machines
> * use modified upload-packages.sh to upload packaged-staging packages
> Feed server:
> * use modified sort.sh to sort the packages by arch and remove old ones
> * generate filelist
> * helperscript gets filelist and does 'for i in $(cat filelist) ; do
> wget -c $i ; done'
> * build will pick up staging packages automatically
> There are a few problems to be solved with that scenario, namely a way
> to get the matching target .ipks as well.
The staging ipkgs contain ipkgs of all the packages generated by a recipe.
> Comments/suggestions/offers for help?
Still working on getting things to work properly but could use some
expert advise too.
I'm not really a python wiz and opkg is a COW (can of worms) too.
>  I might be wrong on that, need to study packaged-staging a bit more
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> -----END PGP SIGNATURE-----
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel at linuxtogo.org
More information about the Angstrom-distro-devel