-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 11.06.2012 20:28, schrieb Chris Rees: > On 11 June 2012 08:57, Alfred Bartsch <bart...@dssgmbh.de> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Am 08.06.2012 22:23, schrieb Chris Rees: >>> On Jun 8, 2012 7:10 PM, "Palle Girgensohn" >>> <gir...@freebsd.org> wrote: >>>> >>>> Chris Rees skrev: >>>>> On 8 June 2012 08:15, Alfred Bartsch <bart...@dssgmbh.de> >>>>> wrote: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>>> >>>>>> Hi, >>>>>> >>>> ... >>>>>> Adding this missing entry to the portstree should solve >>>>>> this issue. To avoid such problems in the future, it >>>>>> would IMHO be preferable to have only one port >>>>>> (/usr/ports/databases/p5-DBD-mysql), which is able to >>>>>> handle all mysql versions, similar to p5-DBD-Pg. >>>>> >>>>> Actually, I'm looking at moving p5-DBD-Pg to versioned >>>>> ports, since it is less unpredictable to install a >>>>> versioned port, the autodetection logic is messy and >>>>> packages are not built for any but the default version. >>>>> >>>>> Chris >>>> >>>> That is partly true, but it is also strange to have a >>>> versioned port where there is no difference other than the >>>> dependency? >>>> >>> >>> Oops, haha, I remember looking at it and also thinking what >>> you just said. Sorry for the noise. >>> >>> Alfred, there actually is a port databases/p5-DBD-mysql which >>> is the only one that ports should depend on (I had this >>> conversation with Alex Dupre IIRC, the maintainer of mysql). >>> >>> I'll do a quick scan for ports depending on the versioned ports >>> and get PRs in. >>> >>> Chris >> >> Thank you for taking care of this. I really would appreciate to >> have only one port as a BDB - MySQL interface. >> >> There is another issue with make index: >> >> Generating INDEX-8 - please wait.. ... Warning: Duplicate INDEX >> entry: jpeg2ps-a4-1.9_2 Warning: Duplicate INDEX entry: >> openldap-sasl-client-2.4.31_1 Warning: Duplicate INDEX entry: >> a2ps-a4-4.13b_4 Warning: Duplicate INDEX entry: c2ps-a4-4.0_1 >> Warning: Duplicate INDEX entry: enscript-a4-1.6.4_5 Warning: >> Duplicate INDEX entry: html2ps-a4-1.0.b7,1 Warning: Duplicate >> INDEX entry: lprps-a4-2.5 Warning: Duplicate INDEX entry: >> mp-a4-3.0.1 Warning: Duplicate INDEX entry: psutils-a4-1.17_2 >> Done. >> >> Related settings in /etc/make.conf: >> >> A4=yes PAPERSIZE=a4 >> >> The index entries for the "-letter" ports are missing >> afterwards. IMHO this primarily happens because the "-letter" >> (slave-) ports are used as master ports for the "-a4" ports. >> >> Are these different ports related to paper format really needed >> anymore - in times of libpaper? >> >> If yes, I would vote for cleaning the ports tree: - - define >> "real" master ports (e.g. print/enscript, print/a2ps) - - change >> the -letter ports to "real" slave ports - - change the MASTERDIR >> entries in "-a4" and "-letterdj" ports - - take care that >> PKGNAMESUFFIX is set in the slave ports only >> >> BTW: There is a tool named p5-FreeBSD-Portindex written by >> Matthew Seaman, which creates a complete index file (=containing >> every port directory), not showing these weaknesses. >> >> The openldap duplicate entry results of setting port option >> "SASL". There is another issue with this port: The package origin >> is stored as net/openldap24-client even with option "SASL" set. >> This port is a dependancy of some kde ports. Every time I'm >> rebuilding one of these ports, portmaster tries to build >> openldap24-sasl-client, even if it is already installed. Manually >> changing the ORIGIN entry in /var/db/pkg solved this issue for >> me. > > You have stumbled upon a known problem. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/162088 > > I'm not quite sure I agree with the closure however, since a > solution is not made, rather a workaround. >
Thank you for esponding. Yes, you are (partly) right. I was the originator of that PR. It was closed due to "out of ideas". This time I chose a direct mailing instead of posting a follow-up to that closed PR. If you'd take another look at my actual post, you will see that this time I'm trying to propose a solution to this "systemic issue", which has been in the ports tree for a very long time. I'm looking forward to your comments. - -- Regards Alfred Bartsch Data-Service GmbH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/W88UACgkQ5QGe2JdVf3jwEwCfX0bFWKx84mUxytOvqYYmGofA IQAAnA8p+WznlOCxyt1oKLUkCsJ2pMiV =yBq1 -----END PGP SIGNATURE----- _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"