> From: Dan Ritter [mailto:d...@randomstring.org] > > Build a Debian Wheezy virtual machine. Run the Debian-supplied > RT package in that. Run apticron so you will get reminders as to > when packages have updated.
If it's better than the centos solution, I'll happily go with it ... Here has been my centos experience: (Centos6 or Amazon linux) Install rt3 from yum. Wrastle. Discover that it's built against mysql, but mysql wasn't installed as a dependency. I think there was also some apache module missing, and apache wouldn't start. Of course, there are no instructions that come along with the yum package installation ... How am I supposed to know what mysql user or database to create? I found a guide written by some guy on the internet, where he started by doing the yum installation, to satisfy as many dependencies as possible, then remove rt3, download source, and start building. At first, I dismissed that guy's guide, and kept wrastling, and slowly resigned myself to accept that he did it the best way possible. I started following his rosy path, until the point "Now, you will have the joy of going through CPAN. In one of my early tries at this, WWW::Mechanize failed and gave a message that it refused to install without using "force." One can google for various solutions, but after a few hours of that, it seemed the majority of people running into this finally said, The heck with it, and used force, as I did. It doesn't seem to have hurt anything." The whole installation process is bogus. I'm having a really hard time believing this is the correct state of the world. In the past, I wrote scripts and procedures to enable the offline caching of CPAN modules installed by the automatic process. For the sake of making CPAN repeatable. Because it's far too often trying to deploy something that depends on CPAN... Stop. I'm following my own tangent that I want to avoid. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
