A few of you have been sending some feature requests
http://code.google.com/p/ubuntutrinux/issues/list
I'm guessing you have to have a google login (thought everybody had
one, hehe) to be able to add issues/bugs, but you might have to be
added to the project. The google code stuff is a lighter weight than
SF. The only real downside is that they only have a 100MB file limit
for downloads, but I think you can request more.
Also I've started at "core tools" wiki page with specific applications
folks have requested. Keep the requests coming.
http://code.google.com/p/ubuntutrinux/wiki/CoreTools
If you look at http://ubuntutrinux.googlecode.com/svn/trunk/prerepo/mkinitramfs
you'll see the build script adds binaries that automatically resolves
shared library dependencies (copy_exec does that magically)
I haven't decided yet if/when to modularize things. The key driver for
modularization (apart from idealism) with the old Trinux was the 1.4MB
limit. But a 1.4MB boot floppy is not feasible with 2.6, even with
uclibc (which I don't want to mess with)
In terms of packaging my current thoughts are to eventually
modify/this script to read in a configuration file automatically
apt-get installs certain apps if they are not available. Basically
having a sort of meta-packaging system that copies over files from the
host. And if there are not Ubuntu packages available (or if they
aren't up to date enough), then I will build .deb's for them and if
the .deb archive gets to be large enough then I will create an
apt-archive.
- mdf
|
