In article <09JAN93.16268680.0012.MUSIC@MARISTB>
KK4D%MARISTB.bitnet@YaleVM.YCC.Yale.Edu (Dan Newcombe) writes:
quoted text
>
>Anyway, what I had in mind was something like:
>
>Program Name:
>Obtained from:  (ftp site and subdirectory)
>Brief Description:  (something like database, cute shoot-em-up game)
>Compiled Under: (Kernel version, GCC version(or whatever lang),
>                 library version)
>Special Dependencies: (stuff like needs X, or Needs CLISP and joystick)
>Needed Changes:  (Changes you had to make.  This is the only part
>                  I'm not sure about.  Maybe I could keep a file
>                  of patches, or where patches could be found.
>                  If it's something small like "undef BLOCK" then that
>                  could be kept here, but I don't want this list to
>                  have stuff like a patch to bring kernel v0.10 up to
>                  v0.99pl2  :)

Excellent! I have thought about the same, and in fact I allready
have xloadimage-info (but some odds there still) and the info
for Prolog (taken from this newsgroup) in the purpose to put them
to FTP site.

I also almost set up a directory to nic.funet.fi:pub/OS/Linux/doc
to compile instructions to compile programs.
(Have to discuss about it with the actual maintainer of
Linux-directory before making anything.)


I have a comment to the last item in your list:
The needed changes should not be a patch file, but similar.

The patch is good place to start, though.
It is good that changes (unclear ones) are described as
why they are done.
Also, if there's multiple similar changes, then it is good
to write the change once, and to list the files where changes
are done.

This way it should be easy to compile the next release even
there's main changes done to the code.


How many items you have in the list, so far?
I suggest that those people who have compiled allready programs
to Linux will write how they did it.
Was that too much to ask?


Juhana Kouhia