Carl Wilhelm Soderstrom wrote: > I put forth my listed points (and a few more) at this page: > > http://backuppc.wiki.sourceforge.net/install_from_package > > I put it under the off-topic section since it really is off-topic > for the > list. I invite others to contribute their views to it; perhaps in a > section > underneath which offers counterpoints and the advantages of compiling > directly from source tarballs. > > I *do* myself compile directly from source tarballs on occasion; but > only on > test machines (like a vmware session), and for purposes of trying > out the > software, and only when there isn't a similar package available.
Woah, this is becoming a large thread. I hope I'm not the one causing this by replying to the 'bad admin' statement. I just wanted to let you know that BackupPC is probably the only piece of software in our infrastructure that I installed from source. I couldn't find a repository that carries a recent version of BackupPC for CentOS 4 and I never mastered the art of packaging stuff myself. I tried it, but found documentation on creating your own RPM's was contradicting other documentation on creating your own RPM's and figured it wasn't worth the trouble for this one piece of software and using the source tarball is just plain easy in BackupPC's case. By the way, there is nothing to compile when installing BackupPC. :o) Nils Breunese. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
