Re: [U4X-Developer] TODO List for 0.1 (psychosis) Release

[Paul M. <le...@ch...>]

On Sun, Mar 04, 2001 at 12:07:28PM -0500, Dean Scott wrote:
> >We should probably nuke our ancient dying version from CVS and import
> the
> >current one to hack upon for 0.2, ideas?
>=20
> Yeah - I'm not quite sure which version of lilo we're going to go with.
> ATM, I'm running lilo 21.7 with SuSe's graphical boot patch. This patch
> is nicer than the redhat one, but seems to have issues with text
> selection. I'll have to fight with it a bit and get back to you.
>=20
Text coloring and proper positioning was one of the issues I ran into when
I was originally hacking up lilo for this stuff. I've never seen SuSE's
patch though, I can take a look at it later if necessary.

> >Also, things like the Ogg Vorbis stuff will need packaging, and the
> ALSA
> >stuff if it hasn't been done already. Stuff like broadcast 2000
> wouldn't
> >hurt either.
>=20
> ok, I'll have to look into bc2000. the other stuff you've asked for was
> already on my paper list, i just didnt copy it over. As to alsa, I'm not
> very familiar with it, which do I package? Just alsa-0.9b.tar.gz or
> whatever? Also, I may package up xine and some of the gatos tools.
>=20
ALSA is split up into 3 components, alsa-driver, alsa-lib, and alsa-utils.
alsa-driver is a bunch of modules that is built for your specific kernel
and shoved in /lib/modules/`uname -r`/misc/ (not at all compliant with the
new modutils, but that can be fixed). alsa-lib is basically all the lame
userspace library stuff that applications like to link against and go
through. and alsa-utils is, as the name suggests, various utilities. Such
as alsamixer/alsactl/etc.

See about getting your list of packages written up in a form we can shove
on the website so we can add packages as we need to and have them marked
as 'todo' or 'done' or whatever.

> Well, this is the main reason for me wanting to have logical groups in
> the spec files. It makes sorting through them much much easier. I'm
> hesitant to actually put the RPMS into different folders however; I've
> found the way SuSe does it to be confusing at times, and having one
> giant dir is fairly easy to find stuff in quickly.=20
>=20
The only reason it's confusing when SuSE does it, is because they use a
braindead naming scheme. They also truncate the filename making it even
more fun to search the repository in search of what you want. As long as
we use simple and to the point directory names, don't screw with the file
names, and have a nice INDEX in the top level directory that lists all of
the files, with a brief description of them (possibly extracted via rpm,
this could be done in a script and croned) then we shouldn't have any
issues with it. My main problem with sticking everything into one
directory is that it makes it an absolute total mess to find what you're
looking for (outside of the installer) and it's about as useless to look
at as the SourceForge UI.

> >> - kernel (i know paul has been pounding on it, worst case is that i
> put
> >> together a kernel with various patches and ship that)
> >>=20
> >Yeah, the stuff in CVS is a wee bit on the busted and out of date side.
> This
> >is definately one of the things we're going to need to work on, as we
> don't
> >have a whole lot to work with at the moment.
>=20
> If you have time to do this, great. If not, I can fold in useful patches
> and we can ship that.
>=20
Yeah, it's already high on my todo list, will start hammering on it some
more as time allows. Feel free to do your own patch though and shove it
on the ftp, always good to have variety.

Regards,

--=20
,----------------------------------------------------,
|       Paul Mundt | Email: le...@ch... |
|   Head Developer | URL:   http://www.u4x.org       |
| Head of Security | URL:   http://www.stampede.org  |
`----------------------------------------------------'