[Angstrom-devel] Maintenance of unstable feed

[Koen Kooi]

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

Paul Sokolovsky schreef:
|> Paul Sokolovsky schreef:
|
|> |   And we really should settle on unstable feed upload procedure,
|
|> contrib/angstrom (in the stable branch) has an upload script people
|> running official autobuilders should use. If it hasn't been built by a
|> autobuilder, it shouldn't be available for download (that includes
images!).
|
|   For the release feeds, fully agree. But should we be the same strict
| for *unstable* feed? Unstable is not official part of the release feeds,
| it's not included in images' feed configs, users must add it
| explicitly, and are supposed to know what they do.
|
|   And it would be nice to have it more open for different developers,
| and to use it as a staging/testing area for the things they work on,
| they intend for stable feed addition, or users ask for the latter. In
| this regard, asking that packages were built from OE-comitted recipes
| and configs should be enough IMHO. Comments?

That leads to a mess faster than Harald can say "GPL violation". User
built package should be exceptions, not the rule in the unstable feed. I
can think if one exception at the moment:

* octave and (lib)gfortran

Since fortan is disabled in the stable branch, we can't build octave.

|> | and invite people to upload more builds.
|
|> No, if it hasn't been built by a autobuilder, it shouldn't be available
|> for download (that includes images!).
|
|   Does that apply for OPIE images too? As I wrote, my idea was to save
| autobuilder from extra load for now. If it's ok if it builds them,
| we'll prepare patches.

The load isn't the problem, so please prepare patches. In a week or two
we'll have a second autobuilder that will do all powerpc builds, so
build load will be even less. A third autobuilder for angstrom 2008.x
should be online soon as well.


|> |   And yeah, we should cleanup feed management scripts - the way it is
|> | currently on serenity is dirty, dirty, dirty.
|
|> Check sort.sh and new-index.sh in the 2007 and 2008 feeds, that is much,
|> much neater.
|
|   Nice, I'll treat those as the master copies, will add path argument to
| them, and then clean up all those various index.sh/new-index.sh lying
| in every subdir of unstable ;-). (Will do as time permits.)

My plan was to absorb new-index.sh into sort.sh and have it mark updated
feeds so we can call update.php more intelligently. I ran out of time
before completing that. Any volunteers?
We probably should sort.sh in ~/bin as well to avoid version skew and
nominating 'master copies'. Any volunteers?
After that we can write an angstrom-feed-upload.bb that automates all
that :)

regards,

Koen

- --
koen at dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi at student.utwente.nl instead.

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

iD8DBQFHflDMMkyGM64RGpERAgJ5AJ9ce/ztBND/wlaXjozH8olybA8CwwCfbHnw
cHIcLWmO5cqtkG+L4scEF54=
=xnLg
-----END PGP SIGNATURE-----