Thus spake Alexander E. Patrakov ([EMAIL PROTECTED]):
> If you want to help, here is a conceptually simple, but long and
> boring task for you. Draw a tree of dependencies between packages on
> the current full CD in dia or anything else that can be easily
> converted to SVG.
As a matter of fact this actually doesn't sound so frightening to me at
all, since for a fair fraction of the packages I have a working
serialized dependency order and notes anyhow. Namely for those packages
which I'm using on my own systems.
But ... what do you actually want? I ask this in terms of aims and
purposes, not in terms of tasks, as I don't understand your reasoning in
creating a graphic (and this even in a specific format).
> For each leaf package that you know how to use, write a short document
> (or a long document, if a package is not simple) explaining how to
> test its basic functionality ("make check" alone doesn't count)
Does "'make check' and look at the output, it should read XXX" count?
What's "basic functionality" of a package? Taking libpng as an example.
Is it enough that a dummy program with a call to png_read_png() can be
compiled and linked, or do you want to verify that a 4-bit color depth
png file can be read correctly?
> You may assume that the test will be run in an emulator such as QEMU,
> KVM or VMware, so instructions to fill the hard disk(s) with arbitrary
> contents are allowed.
This really sounds a bit like "please create exhaustive test cases for
our 240 packages".
> > And maybe updating the remastering hint on
> > http://www.linuxfromscratch.org/hints/read.html with the current
> > version from svn.
>
> Hm, aren't they currently the same?
Hints web page: 2007-08-28
svn trunk/doc/: 2007-11-28
I wouldn't have made that comment if they were the same.
Hendrik
--
Those who give up essential liberties for temporary safety
deserve neither liberty nor safety. -- Benjamin Franklin
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
