Re: devel/autotools267 and UPDATING
Am 16.09.2010 01:30, schrieb Barbara: I've just run portupgrade -ap, after getting the new autotools and reading UPDATING. From what I can understand, as it's not a version bump but a new port (I realized it too late...). So maybe I should have used something like: # portupgrade -o devel/autoconf267 autoconf262 Am I wrong? If not, maybe a note in UPDATING should be needed. Now I have: $ pkg_info -Ix autoconf-2.6 autoconf-2.62 Automatically configure source code on many Un*x platforms autoconf-2.67 Automatically configure source code on many Un*x platforms And about the dependencies: $ pkg_info -Rx autoconf-2.67 Information for autoconf-2.67: $ pkg_info -Rx autoconf-2.62 Information for autoconf-2.62: Required by: automake-1.10.3 automake-1.11.1 automake-1.4.6_6 automake-1.5_6,1 automake-1.6.3_2 automake-1.7.9_3 automake-1.8.5_4 automake-1.9.6_4 autotools-20100915 So it seems that all the rebuilt ports depends on autoconf-2.62 and so I don't know anymore which were the ports bumped for the dependency with the new version to rebuild it after removing autoconf-2.62. I've reinstalled autotools with portmaster (in ports/ports-mgmt/portmaster) to solve this. Might be worth a try. -- Matthias Andree ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/autotools267 and UPDATING
On 16/09/2010 11:43:04, Matthias Andree wrote:
Am 16.09.2010 01:30, schrieb Barbara:
I've just run portupgrade -ap, after getting the new autotools and reading
UPDATING.
From what I can understand, as it's not a version bump but a new port (I
realized it too late...). So maybe I should have used something like:
# portupgrade -o devel/autoconf267 autoconf262
Am I wrong? If not, maybe a note in UPDATING should be needed.
Now I have:
$ pkg_info -Ix autoconf-2.6
autoconf-2.62 Automatically configure source code on many Un*x
platforms
autoconf-2.67 Automatically configure source code on many Un*x
platforms
And about the dependencies:
$ pkg_info -Rx autoconf-2.67
Information for autoconf-2.67:
$ pkg_info -Rx autoconf-2.62
Information for autoconf-2.62:
Required by:
automake-1.10.3
automake-1.11.1
automake-1.4.6_6
automake-1.5_6,1
automake-1.6.3_2
automake-1.7.9_3
automake-1.8.5_4
automake-1.9.6_4
autotools-20100915
So it seems that all the rebuilt ports depends on autoconf-2.62 and so I
don't
know anymore which were the ports bumped for the dependency with the new
version to rebuild it after removing autoconf-2.62.
I've reinstalled autotools with portmaster (in ports/ports-mgmt/portmaster) to
solve this. Might be worth a try.
autotools are generally just build dependencies for any of the ports
that you'ld want run on a machine -- ie. they only need to be there at
the point you build the port. Once you've installed whatever it is, you
can delete just auto{conf,make} etc. portmaster(1) even has options to
do that automatically.
You'll tend to end up with many different versions of autotools
installed over time, as ports get updated to use more recent versions.
Occasionally purging them all does no harm, and will save you a small
amount of disk space.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
devel/autotools267 and UPDATING
I've just run portupgrade -ap, after getting the new autotools and reading UPDATING. From what I can understand, as it's not a version bump but a new port (I realized it too late...). So maybe I should have used something like: # portupgrade -o devel/autoconf267 autoconf262 Am I wrong? If not, maybe a note in UPDATING should be needed. Now I have: $ pkg_info -Ix autoconf-2.6 autoconf-2.62 Automatically configure source code on many Un*x platforms autoconf-2.67 Automatically configure source code on many Un*x platforms And about the dependencies: $ pkg_info -Rx autoconf-2.67 Information for autoconf-2.67: $ pkg_info -Rx autoconf-2.62 Information for autoconf-2.62: Required by: automake-1.10.3 automake-1.11.1 automake-1.4.6_6 automake-1.5_6,1 automake-1.6.3_2 automake-1.7.9_3 automake-1.8.5_4 automake-1.9.6_4 autotools-20100915 So it seems that all the rebuilt ports depends on autoconf-2.62 and so I don't know anymore which were the ports bumped for the dependency with the new version to rebuild it after removing autoconf-2.62. Barbara ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
devel/autotools267 and UPDATING
About my previous mail, shouldn't the upgrade be handled by the entry in MOVED? Is it a portupgrade problem? Is the rebuild of ports like xmms or libX11 really necessary after a new version of autoconf? Thanks Barbara ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/autotools267 and UPDATING
Hi, all-- On Sep 15, 2010, at 4:43 PM, Barbara wrote: About my previous mail, shouldn't the upgrade be handled by the entry in MOVED? Is it a portupgrade problem? Is the rebuild of ports like xmms or libX11 really necessary after a new version of autoconf? It looks like maybe a repocopy is going on (or has gone wrong), since it is pointing to autoconf-2.62: # pwd /usr/ports/devel/autoconf267 # cat distinfo MD5 (autoconf-2.62.tar.bz2) = e1fb8fe0b22e651240afdfa2be537a3c SHA256 (autoconf-2.62.tar.bz2) = 42be7628e32fd3bebe07d684b11fb6e7e7920ef698fc4ccb3da6d77f91cefb96 SIZE (autoconf-2.62.tar.bz2) = 1165951 # head Makefile # New ports collection makefile for:autoconf262 # Date created: 7th December 2006 # Whom: a...@freebsd.org # # $FreeBSD: ports/devel/autoconf267/Makefile,v 1.75 2009/12/16 11:21:25 linimon Exp $ # PORTNAME= autoconf PORTVERSION=2.62 CATEGORIES= devel Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
devel/autotools267 and UPDATING
First of all, sorry about the error in subject (s/autotools/autoconf/). I've noticed the problem with the first commit on freshports, while running portsnap. So I run portsnap again till a new snapshot containing the new version were fetched. In fact I have: $ cat /usr/ports/devel/autoconf267/distinfo MD5 (autoconf-2.67.tar.bz2) = 3fbf92eb8eaca1e0d33dff9710edb5f0 SHA256 (autoconf-2.67.tar.bz2) = 00ded92074999d26a7137d15bd1d51b8a8ae233a6cd165a38f34ccf7b1a78aef SIZE (autoconf-2.67.tar.bz2) = 1369605 Thanks Barbara ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/autotools267 and UPDATING
On Sep 15, 2010, at 4:43 PM, Barbara wrote: About my previous mail, shouldn't the upgrade be handled by the entry in MOVED? Is it a portupgrade problem? Is the rebuild of ports like xmms or libX11 really necessary after a new version of autoconf? With sweeping ports such as autotools, the consensus is to bump PORTREVISIONs on affected dependent ports, even if they are build dependencies only. We've tried in the past to get creative in what does and doesn't get bumped, and it always generates more problems than it solves. On Sep 15, 2010, at 18:48 , Chuck Swiger wrote: It looks like maybe a repocopy is going on (or has gone wrong), since it is pointing to autoconf-2.62: You need to update your ports tree. Makefile is revision 1.77, not 1.75 as you have shown. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/autotools267 and UPDATING
Hi, Ade-- On Sep 15, 2010, at 5:13 PM, Ade Lovett wrote: On Sep 15, 2010, at 18:48 , Chuck Swiger wrote: It looks like maybe a repocopy is going on (or has gone wrong), since it is pointing to autoconf-2.62: You need to update your ports tree. Makefile is revision 1.77, not 1.75 as you have shown. Oh, I did-- but it seems like cvsup8.FreeBSD.org is running behind. I switched to a different cvsup server and /usr/ports/devel/autoconf267 looks sensible now. Thanks for the feedback, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
