(I am adding freebsd-ports@ to the thread as you suggested)
Xin LI wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, Panagiotis,
>
> Panagiotis Christias wrote:
>> Hello,
>>
>> I came across another dependency bug. It looks like packages that depend
>> on net/openldap24-client (e.g. mail/sendmail-ldap, mail/dovecot with
>> WITH_LDAP=true etc) fail to register the openldap dependency in systems
>> that have net/openldap24-sasl-client port installed.
>
> I am aware of this problem but I don't have a good solution for it (at
> hand), this is an infrastructural issue with the ports dependency
> tracking - if two ports installs exactly the same files, there is no way
> to distinguish between the two without forcing to install one even if a
> conflicting one is already installed.
Hm.. messy. How does lang/perl5.[6,8,10] handle such problems?
> Can we post this to -ports@ so we can bring more people into the
> discussion? I think this would be an interesting topic that should have
> been addressed sooner than later.
>
> (By the way, as a workaround portupgrade(1) for instance can be
> configured to force specified dependency, just FYI;).
Are you referring to something like the following in pkgtools.conf?
ALT_PKGDEP = {
'net/openldap24-client' => 'net/openldap24-sasl-client',
}
I am already using that. Without it portinstall/upgrade would try every time
to install net/openldap24-client (and fail). But it still does not register
the dependency.
Regards,
Panagiotis
--
Panagiotis J. Christias Network Management Center
p.chr...@noc.ntua.gr National Technical Univ. of Athens, GREECE
Panagiotis Christias wrote:
> Hello,
>
> (I am adding freebsd-ports@ to the thread as you suggested)
>
>
> Xin LI wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi, Panagiotis,
>>
>> Panagiotis Christias wrote:
>>> Hello,
>>>
>>> I came across another dependency bug. It looks like packages that depend
>>> on net/openldap24-client (e.g. mail/sendmail-ldap, mail/dovecot with
>>> WITH_LDAP=true etc) fail to register the openldap dependency in systems
>>> that have net/openldap24-sasl-client port installed.
>>
>> I am aware of this problem but I don't have a good solution for it (at
>> hand), this is an infrastructural issue with the ports dependency
>> tracking - if two ports installs exactly the same files, there is no way
>> to distinguish between the two without forcing to install one even if a
>> conflicting one is already installed.
>
> Hm.. messy. How does lang/perl5.[6,8,10] handle such problems?
Install an entry into /etc/make.conf, I think it's Ok for perl (since
there are a lot of ports depends on it) but not for OpenLDAP...
Cheers,
- --
Xin LI <del...@delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkoUjvoACgkQi+vbBBjt66CxQgCgt5nbavwhqigC0olet1AJWO30
xVsAn28lB+20KTGRjKg1cSo3rjFL2aEq
=tTlz
-----END PGP SIGNATURE-----
Ok, then how about dropping the net/openldap24-sasl-client port and adding
an SASL OPTIONS entry to the net/openldap24-client port, like the server port?
> I am already using that. Without it portinstall/upgrade would try every
> time to install net/openldap24-client (and fail). But it still does not
> register the dependency.
There is a "knob" for this problem that should help you, please add
WANT_OPENLDAP_SASL=YES
to your /etc/make.conf.
I also ran into this problem and this solved it for me. There are more
options for openldap (documented in /usr/ports/Mk/bsd.port.mk).
Uwe
> Ok, then how about dropping the net/openldap24-sasl-client port and
> adding an SASL OPTIONS entry to the net/openldap24-client port, like
> the server port?
Then those who use packages will loose a possibility to use
"pkg_add -r".
WBR
--
bsam
Yes, this is the problem with packages like net/openldap24-server,
mail/sendmail but at least they do not break the dependency chain which
I consider fundamental. On the other hand, the possibility to use
"pkg_add -r" is an additional desired feature, but, never the less, a
feature.
You are right, problem solved! The funny thing is I was already using
WANT_OPENLDAP_VER for a long time. I suppose back then, I failed notice the
other options :)
Thanks a lot,