On Mon, Jun 19, 2006 at 11:03:32PM +1000, Adam Kennedy wrote: > Except that you wouldn't expect a Perl installer to install full copies > of MySQL server, and Postgres server, and whatever else someone might > use, which was the context of the thread. I would love to see more dependency information on perl packages, in the META.yml files, on things like "I need a database, more or less any database", and "I need a copy of the program gtk-config in my PATH" that installers could make decisions based on. Sadly, it appears that there isn't space available within the requires-format keys, which would be ideal. (requires, build_requires, recommends, conflicts). I would suggest adding versions of them suffexed by "2", or "-2", and making the keys for the existing ones say "package:". Then we can add "os:", "header:", and "executable:" spaces, and make the rule that older installers, when faced with a space they don't know how to handle, should warn on all requirements in it, but otherwise ignore them (IE assume they are satasified for everything but "conflicts".) (An "installed size" field would also be lovely, but calls very much for computation by the thing creating the META.yml, rather then a statement by the developer.) -=- James Mastros