At 19:28 Uhr -0500 14.02.2002, David R. Morrison wrote: >I like the > >SplitOff: << > Package: %n-shlibs ><< > >style. But I have a question about the syntax: will the entries within >a "SplitOff" section be allowed to use multi-line format themselves? e.g. > >SplitOff: << > Package: %n-shlibs > DescDetail: << > The shared libraries for foo have many special properties which must > be discussed in detail here > << ><< > >I'm a bit worried about getting this parsed (by humans or by perl).
Hm. I personally have no troubles reading it when proper indention is applied. It should be feasible to allow the parser to handle it, too. But we could also resort to a different marker set for the inner multi line field, e.g. instead of "<<" use "{{" or "[[" or so. >Also, which things are allowed in SplitOff? Which things will have a >default value? This requires some thought... My current list (incomplete): Required: Package Allowed: Files (only allowed inside splitoff) Shlibs Depends Recommends Description DocFiles License Inherited: Version (cannot be changed in splitoff) Revision (cannot be changed in splitoff) Maintainer (cannot be changed in splitoff) Homepage (cannot be changed in splitoff) Description DocFiles License Explicitly forbidden: *Script (CompileScript, PatchScript etc.) Patch Source* NoSource* Type* Update* Set* NoSet* (basically, anything that is build related) Cheers, Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel