Date: Sun, 7 Feb 2010 06:56:44 -0500 From: Jerry <gesbbb@yahoo.com> To: freebsd-ports@freebsd.org Subject: Re: better way to handle required rebuild on library bump Message-ID: <20100207065644.747507f6@scorpio.seibercom.net> In-Reply-To: <a0777e081002061348w2df8927brcc247ce0e3fdf5c7@mail.gmail.com> References: <a0777e081002061348w2df8927brcc247ce0e3fdf5c7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 6 Feb 2010 23:48:33 +0200 Eitan Adler <eitanadlerlist@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 kind of MAJORVERSION be stored in /var/db/ports. > Then when a library's MAJORVERSION is changed it will prompt a > rebuild on any port that relies on it will also get rebuilt. > Computer are *designed* handle these types of things This will accomplish exactly what you want: portmanager -u -p It is in the port tree. -- Jerry gesbbb@yahoo.com |::::======= |::::======= |=========== |=========== | We are not a clone.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100207065644.747507f6>