Date: Wed, 13 Mar 2002 01:43:33 +0900 From: "Akinori MUSHA" <knu@iDaemons.org> To: Mikhail Teterin <mi@aldan.algebra.com> Cc: roam@ringlet.net, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/graphics/autotrace Makefile ports/graphics/graphviz Makefile ports/graphics/libafterimage Makefile ports/graphics/librsvg Makefile ports/graphics/libwmf Makefile ports/graphics/sdl_ttf Makefile ports/print/ft2demos Makefile ... Message-ID: <86wuwhag96.wl@archon.local.idaemons.org> In-Reply-To: <200203121554.g2CFsi3b073497@aldan.algebra.com> References: <86zo1daofp.wl@archon.local.idaemons.org> <200203121554.g2CFsi3b073497@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 12 Mar 2002 10:54:44 -0500 (EST),
Mikhail Teterin wrote:
> > Unfortunately, this is not sufficient because someone removed the
> > shlib major part of freetype2 and some other libraries' LIB_DEPENDS
> > entries from his ports. You should grep for -w freetype2 instead to
> > catch by the port name.
>
> I did. And you know my reasoning, which I don't find unfortunate at all.
> All those ports will build with ANY freetype, and handling the binary
> upgrades is not the ports system's primary objective. Hardly even
> secondary.
I don't particularly object to your chagens by now, but I cannot fully
agree with that. Handling upgrades is not a priority, but making
ports-current work with older installation is not a priority either.
I think people want to upgrade packages just as they want to build
ports with older libraries. It's hard to decide which should come
first, but as long as they don't conflict, let each of us do the best.
> >> I will commit a patch updating those three ports in a minute, but
> >> please take note of this situation and try not to miss "hidden"
> >> dependencies in the future! :)
>
> If you plan on backing out my changes, I'll, probably, put them back
I don't have the authority nor such a plan. I'm going to do proper
PORTREVISION bumps only, and I was just saying that he was missing
your changes and looked confused. And that was my concern, actually.
> in promptly -- you are yet to convince me they are wrong. Yours,
In the last discussion, some people expressed anxiety that people
might neglect bumping PORTREVISIONs because of your changes. Do you
remember?
So, I might as well suggest you join my preaching about forgotton
PORTREVISION bumps as a compensation. :)
> > Anyhow, let's do bump PORTREVISION's ourselves whenever we find this
> > kind of incomplete library port upgrade. :)
> >
> > Or users may just get lost.
>
> This means the upgrade mechanism is incomplete. If portupgrade (or
> whatever tool is used) upgrades port A, which results in a shared
> library bump of libA, it should automaticly upgrade all ports B, C, D
> which LIB_DEPEND on libA -- without an explicit PORTREVISION bump in B,
> C, and D.
Oh, thanks for the hint. :)
I'll add the feature to portupgrae in the future, although it's not
very easy to implement.
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"Somewhere out of a memory.. of lighted streets on quiet nights.."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wuwhag96.wl>