Re: better way to handle required rebuild on library bump

2010-02-08 Thread Eitan Adler
With due respect to the creativity of the OP, the whole conversation is basically moot since in almost all cases a library major version change requires a change to the LIB_DEPENDS line in the port anyway, so a PORTREVISION bump is a very tiny bit of additional work. Ah, I did not realize this.

Re: better way to handle required rebuild on library bump

2010-02-07 Thread Jerry
On Sat, 6 Feb 2010 23:48:33 +0200 Eitan Adler eitanadlerl...@gmail.com articulated: The recent change to jpeg required a lot of changes to a lot of ports all just to bump a version number. It is easy to miss things this way and requires a lot of work and downloading. I propose that some

Re: better way to handle required rebuild on library bump

2010-02-07 Thread Eitan Adler
This will accomplish exactly what you want: portmanager -u -p How will portmanager -u -p avoid the need to bump the PORTREVISION (like the recent jpeg change)? It is in the port tree. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | We are

Re: better way to handle required rebuild on library bump

2010-02-07 Thread Buganini
I thought about this during last jpeg update: http://www.mail-archive.com/freebsd-ports@freebsd.org/msg22476.html http://www.mail-archive.com/freebsd-ports@freebsd.org/msg22501.html but this need non-trivial work on mk, and somebody may consider it too complicated. --Buganini

Re: better way to handle required rebuild on library bump

2010-02-07 Thread b. f.
I've been using portmaster since I started using freeBSD (about 2 and a half years ago) ;) My post was a way to deal with things like the recent jpeg update in a more efficient manner. Instead of the port committer having to bump the portrevision of each port that depeneds on jpeg they could just

better way to handle required rebuild on library bump

2010-02-06 Thread Eitan Adler
The recent change to jpeg required a lot of changes to a lot of ports all just to bump a version number. It is easy to miss things this way and requires a lot of work and downloading. I propose that some kind of MAJORVERSION be stored in /var/db/ports. Then when a library's MAJORVERSION is

Re: better way to handle required rebuild on library bump

2010-02-06 Thread Edwin Groothuis
On Sat, Feb 06, 2010 at 11:48:33PM +0200, Eitan Adler wrote: The recent change to jpeg required a lot of changes to a lot of ports all just to bump a version number. That is true, there is a script for in /usr/ports/Tools/scripts/ called bump_version.pl which can do most of the magic. It is

Re: better way to handle required rebuild on library bump

2010-02-06 Thread Eitan Adler
On Sun, Feb 7, 2010 at 12:27 AM, Edwin Groothuis ed...@mavetju.org wrote: On Sat, Feb 06, 2010 at 11:48:33PM +0200, Eitan Adler wrote: The recent change to jpeg required a lot of changes to a lot of ports all just to bump a version number. That is true, there is a script for in