On Sat, Aug 06, 2005 at 10:55:01AM -0400, Kevin Horton wrote: > I had seen that, but was hoping for a bit more. But, if that is all > there is I will try to clarify a few things: > > 1. These examples suggest that the info2 portion can be imbedded in a > "regular" .info file. I.e. I don't need to have the "Info2: <<" at > the top of the file. But, if I look at the .info files on my HD, I > can only find the "Info2: <<" at the top of the file. Does the whole > info file need to be inside the Info2 block?
There's an entry for "InfoN" in the Fields section of the Packaging Manual. There, it is explicitly stated: "embed the entire package description in the desired InfoN field." That means... > 2. I can only use the %type_raw[] and %type_pkg[] pseudo-hashes > inside the info2 portions of the .info file. Is this correct? doesn't have any meaning. > 3. The only new capability that using info2 adds is the ability to > use %type_raw[] and %type_pkg[] pseudo-hashes. Is this correct? InfoN for N>=2 allows you to have percent-expansion in the Package field of the main package (as documented in the entry for the Package field). The entry for "InfoN" should (but does not:( list the specific meaning of each N level. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
