Re: Multiple port versions
Hi, On Wednesday 03 January 2007 16:33, Vizion wrote: Just been doing a check on installed applications. pkg_info shows multiple installed versions of autoconf, automake, db gnupg. viz: autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.53_3 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms automake-1.4.6_2GNU Standards-compliant Makefile generator (1.4) automake-1.5_2,1GNU Standards-compliant Makefile generator (1.5) automake-1.9.6 GNU Standards-compliant Makefile generator (1.9) It is ok (and even neccessary) that you have different autoconf/automake versions installed. This is because different projects use different versions of this package. And these versions are not compatible. A port that uses automake-1.5 will not compile with automake-1.9. You therefore need all these versions of autoconf and automake. db4-4.0.14_1,1 The Berkeley DB package, revision 4 db42-4.2.52_5 The Berkeley DB package, revision 4.2 This might be a similar problem. If you look at the ports, then you will see that there are quite a few versions of the db package available. Maybe there are ports that depend on 4.0 and won't work with 4.2. I'm not sure if it is a good idea to remove the older version. gnupg-1.4.6_3 The GNU Privacy Guard gnupg-2.0.1 The GNU Privacy Guard You can savely remove gnupg-1.4.6_3. Version 1.4.6_3 was the gnupg port and 2.0.1 was the gnupg-devel port. Version 1.4.6_3 is now obsolete and you can savely remove it. I used partupgrade -aF recently when, on reconsideration, it would have been better to have done portupgrade -F on specific ports! What is the safest way to remove the earlier versions? You can remove them the normal way with pkg_delete package. E.g. pkg_delete gnupg-1.4.6_3 Best regards, Lothar pgp3qIFkJbuX8.pgp Description: PGP signature
Multiple port versions
Just been doing a check on installed applications. pkg_info shows multiple installed versions of autoconf, automake, db gnupg. viz: autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.53_3 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms automake-1.4.6_2GNU Standards-compliant Makefile generator (1.4) automake-1.5_2,1GNU Standards-compliant Makefile generator (1.5) automake-1.9.6 GNU Standards-compliant Makefile generator (1.9) db4-4.0.14_1,1 The Berkeley DB package, revision 4 db42-4.2.52_5 The Berkeley DB package, revision 4.2 gnupg-1.4.6_3 The GNU Privacy Guard gnupg-2.0.1 The GNU Privacy Guard I used partupgrade -aF recently when, on reconsideration, it would have been better to have done portupgrade -F on specific ports! What is the safest way to remove the earlier versions? Thanks David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multiple port versions
In the last episode (Jan 03), Vizion said: Just been doing a check on installed applications. pkg_info shows multiple installed versions of autoconf, automake, db gnupg. viz: autoconf-2.13.000227_5 Automatically configure source code on many Un*x platforms autoconf-2.53_3 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms automake-1.4.6_2GNU Standards-compliant Makefile generator (1.4) automake-1.5_2,1GNU Standards-compliant Makefile generator (1.5) automake-1.9.6 GNU Standards-compliant Makefile generator (1.9) db4-4.0.14_1,1 The Berkeley DB package, revision 4 db42-4.2.52_5 The Berkeley DB package, revision 4.2 gnupg-1.4.6_3 The GNU Privacy Guard gnupg-2.0.1 The GNU Privacy Guard Those are all separate ports that don't conflict with each other. You can check by running pkg_info -L on a couple of them and see that they either install into their own subdirectories, or have version prefixes on their files. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Multiple port versions
Vizion writes:
What is the safest way to remove the earlier versions?
By not doing so.
Different ports use different versions of the same program;
this especially true with things like automake and autoconf.
(In the latter two instances there's a push on to unify some or all
of these ... but that day is not today.)
If I _had_ to do this, I would:
run pkgdb -F
for each port {
run pkg_info -R on each port
if and only if no other ports are listed under required
by, delete the port
run pkgdb -F
}
Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Multiple port versions
Just a quick thank everyone who responded so helpfully.. I guess its a case of leaving sleeping dogs well alone!! chuckles \ Thanks v much david ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multiple port versions
On 1/3/07, Vizion [EMAIL PROTECTED] wrote: What is the safest way to remove the earlier versions? I think if you portupgrade the apps that require those, like portupgrade -R name then it'll upgrade both the app and the required port, removing the duplication. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
