better way to handle required rebuild on library bump
eitanadlerlist at gmail.com
Sun Feb 7 07:32:25 UTC 2010
On Sun, Feb 7, 2010 at 12:27 AM, Edwin Groothuis <edwin at 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 /usr/ports/Tools/scripts/
> called bump_version.pl which can do most of the magic.
I didn't know that - this solves /most/ of the issue.
> > It is easy to miss things this way and requires a lot of work and
> > downloading.
> Oh, you are talking about the user side of things. Please have a
> look at portmaster or portupgrade, they can do this magic for you.
> No, I am talking about the committer's side of things. It is easy to miss a
port that depends on the library your changing.
> > 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.
> I like the idea, but it handles the problem from the wrong side:
> The person who bumps the port revisions would need to have all ports
> installed to make this judgement.
Why? This would be done at the same time that bumping revisions would have
More information about the freebsd-ports