Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Jun 2004 18:59:33 +0200
From:      Ulrich Spoerlein <q@uni.de>
To:        ports@freebsd.org
Subject:   Re: RFC: Re-work pkgdep/DEPORIGIN?
Message-ID:  <20040607165933.GB765@galgenberg.net>
In-Reply-To: <20040607152752.GD9227@spamcop.net>
References:  <20040607152752.GD9227@spamcop.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--FkmkrVfFsRoUs1wW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, 07.06.2004 at 11:27:52 -0400, Jim Trigg wrote:
> > The real fix is IMHO not to blindly record the dependancy provided in
> > the Makefile. That is:
>=20
> > LIB_DEPENDS+=3D   pq.3:${PORTSDIR}/databases/postgresql7-client
>=20
> > will record databases/postgresql7 as dependancy, no matter what package
> > actually provided the libpq.so.3 in the first place. Postgres is not the
> > only place where this is wrong, lang/php4 has the same problems. Most
> > Ports require www/mod_php which I dont have installed. Instead I'm using
> > lang/php4 with WITH_APACHE.
>=20
> The real fix IMHO is to use a strategy similar to what Debian Linux
> uses: instead of depending on specific ports, depend on capabilities.=20
> So for example, www/horde2 would depend on webphp, and lang/php4 and
> www/mod_php4 would each provide webphp.  (I don't know the postgres port
> family as well, so I can't readily give an example using it.)

I don't know the specific debian facilities, but isn't this overkill?
There are mostly two or three ports that come into consideration when satis=
fying
a dependancy (postgresql and postgresql-client, or lang/php4 and
www/mod_php4, or linux_base-{6,7,8}). Most of the times these are even
slave ports (I think), so providing elaborate capabilities management is
overkill IMHO. I know that Debian provides a MTA capability (Postfix,
Exim, Sendmail), but Ports that work with all three of them mostly
require special flags for compilation, don't they?=20

As I said, the quick fix is IMHO to have the "real" origin recorded in
pkgdep at the Registering stage. This is rather trivial to add (or I'm
overlooking some big issues).

Ulrich Spoerlein
--=20
PGP Key ID: F0DB9F44				Get it while it's hot!
PGP Fingerprint: F1CE D062 0CA9 ADE3 349B  2FE8 980A C6B5 F0DB 9F44
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."	-- Benjamin Franklin

--FkmkrVfFsRoUs1wW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAxJ71mArGtfDbn0QRAvQMAKD23494w2OKHlx9zMgpJQ+l0ey00ACcDoL8
Q/tX6Ie56X/L/naNVscFFnE=
=7x5/
-----END PGP SIGNATURE-----

--FkmkrVfFsRoUs1wW--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040607165933.GB765>