Hi, Dirk! On Thu, Jan 04, 2007 at 04:05:05PM +0100, Dirk Nehring wrote: > sorry, I cannot follow it. I do not understand what do you mean with > > "provide certain information about the part they belong to which has to > be shared between different parts".
Well, this sentence describes how exactly redundancy will be reduced through these files: equal information which up to now exists at different places (i.e. "has to be shared between different parts") will exist at one single place (the info.nfo file), but only the information that also belongs together (information about a single part), so each file belongs to a certain part of the build system, for now think of "parts" as of "packages". > Please explain what is the goal of these files? Do you want to > generate documentation? Where is the redunance actually? The exact content of these files is not fixed yet, but this is a sample use of them, holding both multi- and single-line documentation of a package, which will be written into it's Config.in and CONTROL file. > One suggestion: I (personally) do not like suffixes which are very > uncommon like ".nfo". Why not to use something like "DESCRIPTION.txt"? Oh, I forgot to mention that critics is allowed in any case, but not when it comes to the naming of the file. I remember very well how three people (namely wbx, tg and me) were sitting together and discussing possible names. "info.nfo" is a symbiosis of our ideas, and I personally think it's 1337ness is at a very high level. Indeed, it is commonly used - by computer artists for naming their ascii-art, and microsoft for naming files holding system-information - I think our interpretation is a good mixture. :) To get you a better image of the files' content, here is sample content that might be held in them when used in the first intended usage (one for each package): - name - version - descriptions - dependencies (in many different flavours) - selects (could also be seen as kind of dependency) - default values Greetings, Phil
pgphYioDxzG2T.pgp
Description: PGP signature
_______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
