On Tue, 10 Oct 2006 01:13:17 +1000, Adam Kennedy wrote: Hi Adam
> If this is all going to be held in some external system outside the > META.yml , which is what read the above as going with now, then by > all means. This is all perfectly workable and fine, changing it > down the track is just fine. > But if we were to put it into META.yml then not getting it right > first time causes issues. OK. So let's use a separate file, e.g. lib.conf. I confess I originally thought META.yml would be the vehicle for this extra info, but let's agree to retire that plan. My first thought for a name was external.abfy, since we're talking about exes and libs external to the module/distro in question, but external is a bit long after one of my dogs bit through the end of my thumb last night, defending a stolen bone. And of course abfy is Anything But Yaml. As for lib.conf: o It can be per-module, but I think per-disto make more sense o Lib is short and well-recognized o .conf can be called standard, at least in Unix-like environments Actually, distro.conf is /much/ clearer, right? A separate file means a separate processing system (good!): o To stop feature-creep in Module::Build o To allow upgrades of the parser independently from M::B As for the format, I would not mind XML, as long as we keep in mind the dangers: o XML fanaticism o XML fanaticism o XML fanaticism all leading to featuritis. I'm hoping a pure Perl parse will do the work, of course, whatever the format. The contents need to be extensible, as in: required_executables: pgp later to become required_executables: pgp, xyz required_libraries: zlib, pnglib I was also originally thinking, very simplistically, the contents of distro.conf would be like declarative statements, but now see them more like triggers, causing the parser to fire off callbacks on a per-target basis. I leave the details as an exercise for the student. -- Cheers Ron Savage, [EMAIL PROTECTED] on 10/10/2006 http://savage.net.au/index.html Let the record show: Microsoft is not an Australian company
