Too frequent/poorly tested bsd.port.mk commits, and general uselessness of p5-FreeBSD-Portindex

[Doug Barton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/26/2013 12:54 AM, Matthew Seaman wrote:
| I'll be happy to fix any problems reported to me, but I need to see
| reports of problems.  Yours is the first mention I've seen of the
| problems you mention.  Now I know about it, a fix will be forthcoming.
| Obvious in retrospect, but I didn't connect the dots at the time those
| OPTIONS changes came out.

Yes, I've been slack in reporting it. I have mostly just been fixing
them by hand, but since I was whining about stuff anyway, I thought I'd
mention it. :)  FWIW, I have a bunch of old-style db/ports directories
still in place from ports I installed before the style switch and
haven't updated yet. So p5-FreeBSD-Portindex should probably handle both
styles.

| As for db4 vs db5 vs db6 -- portindex doesn't use the extended
| capabilities of db, just an on-disk key-value store.  That should "just
| work" with any version of db.  Upgrading from db4 to db5 almost
| certainly won't work: you should cache-init again.

Yes, I did cache-init after each change of bdb version. I sent a
followup post with a bunch of errors from portindex, but I think they
are related to underlying ports problems as they happened with db47 as
well as db5. The resultant INDEX seems to work Ok in spite of those
errors, but I haven't pushed it very hard yet.

Thanks for the response. :)

Doug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQEcBAEBCAAGBQJSu/DiAAoJEFzGhvEaGryEN1sH/2KMCl3oaW76XPVsAD5HPjNW
SV3rY9cvPDacxn3a1HGJaz83AcxZ24ENoFJX8IztyGlxjYBFk8tGXe0ho04V2NOf
KrfNQEZEI4gtT++tj9z3cfHfwBTJQVjn8vl7x6b+AJxL6vUpV1YrArdSxrLkxbjS
nj+b8Mpb7oT4SlwtNNhtR+9AOxyFqJiPgbgsTXpcTMXFpKNGtk/srsdcw+RvtdpY
brd2nI4EOnjpqxWIO8Ivi9tZn+R9nTi9P5nS3NR9sFkfPDFhR9tCMhsu9rLoI4sA
scxaIBcS/3HKwhk3x0VYqFUrWGlD7g5KXjjyozy1OMMttabV2XpRgM+JewbuhJE=
=C0iT
-----END PGP SIGNATURE-----