laziness, impatience, and hubris | |
PerlMonks |
Module dependenciesby Stegalex (Chaplain) |
on Apr 03, 2002 at 15:04 UTC ( [id://156323]=perlquestion: print w/replies, xml ) | Need Help?? |
Stegalex has asked for the wisdom of the Perl Monks concerning the following question:
I am developing some XML munging Perl right now that has required me to install CPAN module after CPAN module. I will find that I need to use a particular library and then when I go to install that lib, I will find that I first need to install some other libraries and so on and so on. Now this doesn't bother me much, but the problem is that after I develop the code I have to hand it over to another group of people (who aren't terribly familiar with things Perlish) and let them install all the modules and my code on a different box. Now since I am a moron and I haven't been keeping a meticulous list of what was installed and in what order, this is going to be a problem. And now we get to the question: Is there an automated means of determining which modules are dependant upon others? If so, is there a way of producing a list that shows a heirarchical order in which modules must be installed? For example: I found out that I needed to use XML::LibXML. In order to install this, you must first go to xmlsoft.org and download and install libxml2. You must also install XML::SAX. But before you can install XML::SAX, you must first install File::Temp and XML::NamespaceSupport. After you do this, you can install XML::SAX. After all that, you can install XML::LibXML. What I would like is an automated means of producing a list as follows: Forgive me if this is totally naive. I like chicken.
Back to
Seekers of Perl Wisdom
|
|