Too frequent/poorly tested bsd.port.mk commits, and general uselessness of p5-FreeBSD-Portindex
Doug Barton
dougb at dougbarton.us
Sat Dec 28 02:13:39 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/26/2013 03:03 PM, Matthew Seaman wrote:
| I've just committed an update to version 3.3 which should address some
| of the issues to do with handling options files.
Happy to say that the latest version now runs without errors on
cache-init and portindex, using db5. Thank you for doing the update.
I rather strongly suspect that the fact cache-init runs without errors
is that work went into fixing the ports I reported broken, so I would
also like to offer thanks to those who did that work.
Meanwhile since I made my original post there have been 2 more commits
to bsd.port.mk. So my other question remains open ... are willy-nilly
commits to that file the new way of the world? If so I can adjust my
expectations accordingly. It's likely that cache-init is still faster
than 'make index', and on those rare occasions when I catch updates
between bsd.port.mk commits cache-init isn't necessary in any case.
Doug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAEBCAAGBQJSvjPLAAoJEFzGhvEaGryEhkMIAKcsW5K8vXwpKrN7WVTWsWwE
QXpY4zPfjGnUY8bJyEvPkioxCO3QIZ6vOMJE7dGX6Gfij3SOpnZ1ty/1mkcQQg5z
WJH+L9m9tcNLd3ixd7Rj/ufSeiiPYxxmxJhuuXU9KbubAH8p0T/lqzpG4aet2Dv0
7Y3C/jLPt2pWi33v9ZcOkyuyV/QqrXQdKfz5V+TACwS4g45aVLZNRrEKOoTbVOrh
i6lHGHXUq+uZ1RlPXrFUwai6bNeptHn7dfIvFWlI98ej9fOuB2qpSmAALB3wQ36h
BBAoItYfQbsKwuZ1LM6NSnP6BIUe6dpwaUCHRpHUPFlb2dClydp5JgfjaGvNtVE=
=Z6P1
-----END PGP SIGNATURE-----
More information about the freebsd-ports
mailing list