[Angstrom-devel] Maintenance of unstable feed

[Paul Sokolovsky]

Hello Koen,

Friday, January 4, 2008, 5:29:16 PM, you wrote:

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

  Well, we don't talk about "users" here, but about developers who
already have SSH access to the server for upload. And it's just RFC
after all. I don't think the GPL matter is too limiting here, if
recipes are in OE mainline. It will be the same "source available on
request" as it is know.

   But if we don't invite people to cooperate on one well-maintained
repo, we push them to setup their own feeds and organize feed
graveyards like http://handhelds.org/moin/moin.cgi/IpkgFeeds

[]

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

  Well, I'm not sure I understand fully what needs to be done and how.
So, I'd start with bottom-up approach, and in the end would do
something else comparing to what you see it as. So, if you started with
it, please finish it too. But indeed, the scripts should be maintained
in well-known SCM, so mtn/contrib, and there's should be one copy in
well-known place.

  .bb would be nice, but not a panacea, there should be tools to
maintain existing feeds (for example, rebuild indexes after removing
broken stuff).

> regards,

> Koen




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