diff options
author | ade <ade@FreeBSD.org> | 2006-02-24 08:35:57 +0800 |
---|---|---|
committer | ade <ade@FreeBSD.org> | 2006-02-24 08:35:57 +0800 |
commit | 668fa4e20cd7a9f3fe387957083d3e5f1377f27c (patch) | |
tree | 44ed2c94e72415b334e560ce8ccf5ed9f4e2d58d | |
parent | 2f38811ed08d49a29900393396a15b50b3ae8226 (diff) | |
download | freebsd-ports-gnome-668fa4e20cd7a9f3fe387957083d3e5f1377f27c.tar.gz freebsd-ports-gnome-668fa4e20cd7a9f3fe387957083d3e5f1377f27c.tar.zst freebsd-ports-gnome-668fa4e20cd7a9f3fe387957083d3e5f1377f27c.zip |
Add some blurb about the recent libtool mega-commit and some suggestions
on how to (carefully) handle the large number of ports affected by this
change.
Approved by: portmgr (implicit)
-rw-r--r-- | UPDATING | 32 |
1 files changed, 32 insertions, 0 deletions
@@ -6,6 +6,38 @@ You should get into the habit of checking this file for changes each time you update your ports collection, before attempting any port upgrades. +20060223: + AFFECTS: all ports using libtool as part of the build process + AUTHOR: ade@FreeBSD.org + + The way in which ports that require libtool to build has been + completely reworked to bring the ports system in line with other + environments, such as Linux, and pkgsrc. + + devel/libtool13 no longer exists. devel/libtool15 has been modified + to (a) install in the canonical locations and (b) remove a number + of long-standing FreeBSD-specific patches that resulted in a very + different libtool than is present on other systems. + + The main visible change will be that a large number of ports have + had their plists modified (we now install libtool .la archives) + and, as such, PORTREVISIONS have been bumped on ~2000 ports (roughly + 1/7th of the tree). + + Unfortunately, there is no simple upgrade path. Short of removing + all packages and reinstalling from scratch, the only other viable + alternative would be careful use of portupgrade. Given the large + number of different ways in which libtool is used by other ports + in the tree, this is a process that is likely to vary considerably + from system to system, and as such, folks should be very mindful + of running automatic updating software, such as portupgrade, making + extensive use of the -n flag (and equivalents for other updaters) + to see what will actually be rebuilt, before actually performing + the upgrade. + + The good news is that the system now in place will make the handling + of libtool-using ports considerably easier going forward. + 20060221: AFFECTS: users of print/acroread7 and the localized versions AUTHOR: hrs@FreeBSD.org |