intrusive PORTREVISION bumping

[Adam Weinberger]

>> (03.14.2005 @ 0013 PST): Mikhail Teterin said, in 1.1K: <<
> > On Sun, 13 Mar 2005 23:43:31 -0500 (EST), Mikhail Teterin  
> > <mi at corbulon.video-collage.com> wrote:
> > 
> > > Why was the PORTREVISION of editors/ooodict-all bumped on Saturday?
> > > According to the log message, it was to "chase the glib20 version".
> > >
> > > The port installs nothing but data and does not even build anything.
> > >
> > > I understand, that keeping track of such things complicates gnome's
> > > upgrade commits, but such gratuitous bumping is going to result in
> > > plenty of automatic reinstalls around the world _for no good reason
> > > whatsoever_...
> > >
> > > Can it, please, be avoided in the future? Thanks!
> > 
> > Yes, if you keep your eyes open.
> 
> > http://lists.freebsd.org/pipermail/freebsd-openoffice/2005-March/001377.html
> 
> You must think, I'm on the openoffice@ list. I'm not. I'm just a user of
> their port(s)...
> 
> I don't think, they ought to be responsible either -- Gnome@'s method of
> determining the dependencies is flawed... Yours,
> 
> 	-mi
>> end of "Re: intrusive PORTREVISION bumping" from Mikhail Teterin <<

We sent a message to all owners of all ports that depended on glib20.
We asked them to tell us any ports that we shouldn't bump PORTREVISION
on. Per usual, they ignored the question entirely.

There were hundreds -- if not thousands -- of ports which needed a
PORTREVISION bump. A good-sized handful of those ports which were bumped
did NOT end up needing one. However, there is simply no way for the
FreeBSD GNOME team to figure out that list. We relied upon maintainers
to tell us what the deal was with their ports.

We really can't make judgement calls about other peoples' ports. We can
only say, "People will have to rebuild the app and will be ensured that
there will be no library problems. And if it's not necessary, the
maintainer will tell us so."

Complaining to us won't help, because we will be following the exact
same procedure for the next release. Your best bet would be to try to
convince the openoffice team to read emails and PRs from time to time.

That being said, if you can think of a better deployment plan for new
glib20 library versions, please let us know!

# Adam


--
Adam Weinberger
adamw at magnesium.net || adamw at FreeBSD.org
adamw at vectors.cx    ||   adamw at gnome.org
http://www.vectors.cx