[Angstrom-devel] Maintenance of unstable feed

[Paul Sokolovsky]

Hello Koen,

Friday, January 4, 2008, 3:03:51 PM, you wrote:

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

> 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?

> | cleanup old stuff even more consistently (morgue/'s, old stuff at all,
> | like older than a year),

> That should probably be a cron job for the morgues, but deleting stuff
> based on date is a bad idea.

  Not that I call for automatic date-based deletions. But over last
year, there were many changes to OE, and some share of packages in
unstable is actually old and gives users at least inconsistent look,
if not action if they try it. Let's remember old SRCDATE'd revision as
an example. Well, I was concerned about look first of all, as the feed
browser is shared across the feeds. Getting rid of *-dbg packages
popping on every second row was good thing IMHO, and we can postpone
further cleanup until the unstable will get fresh load.

> | 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.

> |   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.)

> regards,

> Koen




-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com