[Angstrom-devel] Maintenance of unstable feed

[Rod Whitby]

Koen Kooi wrote:
> Rod Whitby schreef:
> | Paul Sokolovsky wrote:
> |>    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
> |
> | I must disagree with this statement.  As a real counter-example, the
> | NSLU2-Linux project has tens of thousands of users, and they *all* use
> | packages from official feeds built by a single autobuilder.  There are
> | no unofficial feeds that we know of, and there are no binary uploads, by
> | anyone, ever.
> 
> I also think it's because different device types have different cultures
> and experiences:
> 
> * The openslug users have a distro that is quite up to date and a
> devteam that is pretty responsive with adding new packages. After a
> certain point the feeds are 'saturated', i.e. have all the packages 90%
> of the users want

Yes, our policy for slugos-packages is that if it compiles then it can
be enabled for the feed.  Since the autobuilder works directly from the
latest OE head, then our developers have direct control over what the
autobuilder builds, with no middle-man involved.

> I think we should have a good look on how the nslu2-linux project
> handles things and if possible improve on that. I think being responsive
> to requests is the biggest part of keeping people to use our feeds.
> Sometimes we have to say "no" to requests (openoffice for wrt routers),
> but that's life.

We simply bitbake <distro>-packages ; bitbake package-index ; and rsync
the deploy/ipk directory structure to the feeds web server without any
further processing.

We allow any dev to modify <distro>-packages, with the only constraint
being that all packages must build on the autobuilder machine (which has
a Makefile-defined set of host packages installed, so people can
replicate it).  If a package fails to compile (and is not trivial to
fix), it is disabled until someone has the time to fix it.

_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel at linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel