The actual dependency list from installing SQL::Translator is:
Class::Base GD GraphViz IPC::Run Graph Heap Math::Bezier IO::Scalar Parse::RecDescent Spreadsheet::ParseExcel OLE::Storage_Lite IO::Scalar Template AppConfig Test::Differences Text::Diff Algorithm::Diff Test::Exception Sub::Uplevel Test::Builder::Tester Text::RecordParser XML::Writer XML::XPath XML::Parser YAML
Looking at this list, I can not understand why I would need GD, GraphViz or Template as I don't need visualizations. And these are not trivial modules to install.
I don't really understand why I would need to install Spreadsheet::ParseExcel when I'm never going to use that (I only want to do MySQL <-> MySQL for a client). I would rather be able to have that be optional rather than being forced to install it.
All in all, I'm forced to install modules of which I'm sure that I'm never going to use them. Worse, several modules just didn't install at all! Particularly GD doesn't install "just like that" without the right libraries pre-installed, and XML::Parser is another one that needs an external library to be properly set up.
I perceive obligatory prerequisites for features I'm never going to use as a nuisance. It makes me seriously consider whether or not I would like to have SQL::Translator as a prerequisite for a module that I'm going to develop.
Liz
In reply to Re: Re: Re: Re: Database File Advice
by liz
in thread Database File Advice
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |