Publish Deb files following releases
ruben at gnu.org
Thu May 27 13:32:51 UTC 2010
> I do prefer stable than bleeding, but in some special cases some
> bleeding features could help to sight new compatibility.
> Some new Toshiba laptops will require the bleeding features to work
Well, we publish our releases every ~6 months, so we try to be as near
to the edge as we can without stepping on the slippery end. :)
> > OTOH, if someone wants to make those images and maintain such a
> > project, we would support it and include it in our repositories.
> > But I hope if a hacker with the skills wants to spend some time
> > helping us she chooses any of our other much more important pending
> > tasks. :)
> Yeah, i think to.
> I thought that this task could be automatized, so there won't be much
> need of attention (only if something changed).
The problem is, it can't be automated. We do not use the linux-libre
tarballs, instead we use the deblobber to clean up the Ubuntu kernel.
We need to use that one instead of the vanilla version from kernel.org
because it includes a set of patches to improve the system integration,
and some extra drivers and backports. But since those extra things are
unknown to the deblobber, we need to manually check if the Ubuntu
changes included anything non-free -they sometimes do-.
And as Ubuntu doesn't publish newer kernel version for a certain
release (i.e. lucid will always use 2.6.32), we would need to backport
them, which is an overkill task and probably a Bad Idea(tm).
More information about the linux-libre