On Saturday 24 July 2004 10:15, Jeff Chan wrote: > FreeBSD "ports" definitely track and resolve dependencies, and I > assume "packages" do also. The main difference between ports > and packages AFAIK is that ports grabs all sources and compiles > from them, whereas packages grabs and installs precompiled > binaries. So the problem of separately tracking installation > databases stepping on each others' installs is a definite > possibility if one tries to use both CPAN and ports/packages > on the same FreeBSD system. > > FWIW Watching ports get installed under FreeBSD is similar to > watching CPAN installations. Lots of fully automated updating of > files and resolution of dependencies. Presumably Linux RPMs > do likewise, but FreeBSD had it first, along with other goodies > like the TCP stack.... :-) > > FWIW2 I'm by no means an expert sysadmin, so I'd appreciate any > feedback on the above. > > Jeff C.
I agree with your comments Jeff. The dilemma is what to do if you want to use a perl module that is not in the ports collection. I've managed to get SpamCopURI working by installing the support modules using ports and manually installing SpamCopURI but it felt a bit messy. Tom Munro Glass
