> > Agreed. But how do you define 'best practices'? I guess the term 'best > practices' is not quite applicable to package management software but rather > to security. IMHO, the best way (best practice) to install software is to get > the source tarball, read README, INSTALL, etc., then compile/install. This > way, you get utmost flexibility and configurability, and the latest release.
This method is exactly the method that creates UNMAINTAINABLE SYSTEMS in the first place. What if you need to upgrade the application you installed with a 'make install' ? How would you know where in your file system the files 'make install' put? What if you wanted to see which files of a package has been modified since it was installed ? What if you needed to install one program into 50 different servers? You are partially correct what you said above in that you need to READ THE friendly documentation, browse the support mailing lists, etc. but you need to create A PACKAGE or adopt someone else's package if you want to install it in a production server. 'make install' KILLS maintainability, and gives hell to the next sysad in line (who will most likely reinstall your server anyway). _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
