Date: Sun, 7 Feb 2010 19:37:49 +0200 From: Eitan Adler <eitanadlerlist@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: better way to handle required rebuild on library bump Message-ID: <a0777e081002070937i33c76c53k61284a3ae4f7a4fc@mail.gmail.com> In-Reply-To: <20100207104417.3764f088@scorpio.seibercom.net> References: <a0777e081002061348w2df8927brcc247ce0e3fdf5c7@mail.gmail.com> <20100207065644.747507f6@scorpio.seibercom.net> <a0777e081002070530o33df85c6pcf36aa2468245210@mail.gmail.com> <20100207104417.3764f088@scorpio.seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> <quote> > Then when a library's MAJORVERSION is changed it will prompt a rebuild on > any > 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'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 bump MAJORVERSION in jpeg and have the rest of the work done magically
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a0777e081002070937i33c76c53k61284a3ae4f7a4fc>