Date: Sun, 7 Feb 2010 10:44:17 -0500 From: Jerry <gesbbb@yahoo.com> To: freebsd-ports@freebsd.org Subject: Re: better way to handle required rebuild on library bump Message-ID: <20100207104417.3764f088@scorpio.seibercom.net> In-Reply-To: <a0777e081002070530o33df85c6pcf36aa2468245210@mail.gmail.com> References: <a0777e081002061348w2df8927brcc247ce0e3fdf5c7@mail.gmail.com> <20100207065644.747507f6@scorpio.seibercom.net> <a0777e081002070530o33df85c6pcf36aa2468245210@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 7 Feb 2010 15:30:29 +0200 Eitan Adler <eitanadlerlist@gmail.com> articulated: > How will portmanager -u -p avoid the need to bump the PORTREVISION > (like the recent jpeg change)? =46rom your original post: <quote> Then when a library's MAJORVERSION is changed it will prompt a rebuild on a= ny port that relies on it will also get rebuilt. </quote> I assumed that you were looking for a program that would force an update of any ports that were dependent upon a changed(updated) port. The command I posted would do that. Perhaps I am just not fully comprehending what you are attempting to accomplish. I have as of yet to not found any other port management program that accomplished that as fully as 'portmanager' does. --=20 Jerry gesbbb@yahoo.com |::::=3D=3D=3D=3D=3D=3D=3D |::::=3D=3D=3D=3D=3D=3D=3D |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | When people have trouble communicating, the least they can do is to shut up. =0D Tom Lehrer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100207104417.3764f088>