On Thu, Jun 22, 2006 at 11:28:45AM -0700, Carl Lowenstein wrote: >require newer packages? I just looked at /etc/apt/sources.list and >all repositories are "woody". I did this a year ago so that I could >keep the existing system coherently updated, while preparing for the >release upgrade from 3.0 to 3.1. But I never did the upgrade.
That's why I started using pkgsrc on Linux, to get same packages on all my OS. >So can I just add some "unstable" repositories and see what happens, >or is this a bad idea? Does "pkgsrc" handle dependencies? Does >"pkgsrc" have dependencies of its own that will trip me up? pkgsrc does handle dependencies very well, it will download and compile them. The thing to watch out for is your PATH. Everything pkgsrc typically lives in the PREFIX /usr/pkg (well also /var/db/pkg, normally you can forget about that, and both are relocatable). Main thing: you don't want /usr/pkg/bin in /etc/profile because a new version of pkgsrc perl could break apt-get or something else. It's not difficult to manage if you know what's going on. eg only put /usr/pkg/bin in the front of PATH for non root, interactive shell use. and supervise the setting of PATH for root, depending on what you are doing. All the pkgsrc stuff looks in /usr/pkg/lib etc, by default. >Should I try building Python2.3 from a source distribution? Remember, >I am not running this on an x86 processor. I don't know about pkgsrc on Alpha, but it does work with a lot of OS/arch. // George -- George Georgalis, systems architect, administrator <IXOYE>< -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
