cvs commit: ports/textproc/libwpd Makefile distinfo

Mikhail Teterin mi+kde at aldan.algebra.com
Thu Jan 5 17:03:40 PST 2006


On Thursday 05 January 2006 05:59 pm, Pav Lucistnik wrote:
= > Because to rebuild the tiny libwpd, which itself is perfectly happy
= > with very old versions of libgsf-1 (>=1.6), one must first rebuild
= > their _entire gnome install_.
= >
= > In the vast majority of cases the LIB_DEPENDS should not spell out
= > particular shared library versions, but bsd.gnome.mk is full of
= > them.

= Yeah, you never know if a single program that have USE_GNOME will need
= the latest and greatest. So we're better safe than sorry.

In preparing for that one future possibility we are all suffering
regularly with forced upgrades. Imagine:

	1) install gnome;
	2) a week later - update the ports tree and try to add a
	   gnome-using port (like libwpd);
	3) notice, you have to rebuild your entire gnome.

The sure price of the "safety" of this far exceeds to potential price of
the "sorry". No excuses...

Sure, portupgrade helps, but -- without full rebuilds -- it creates
the shared library mixes, that have their own "sorry" potentials (and
performance costs).

Considering, that most software that has such version demands makes
its own checks in the configure, there is no added safety at all...

= You could add a real LIB_DEPENDS line with >=1.6 to libwpd, right?

Better for those few (if any!) ports, that do need a particular version,
to add their explicit requirements, than for everybody else to do the
opposite.

And no, I can't do it in my port, because bsd.gnome.mk will append its
own (based on USE_GNOME) anyway.

	-mi




More information about the cvs-ports mailing list