Hi Tino, Tino Didriksen writes: > Fixed in svn r64374. I wonder why this doesn't break the build on Debian > Sid.
Thanks. OpenBSD uses a custom pkg-config, not FDO. This difference in behavior is probably a bug on our end. > You should use svn exports pegged to a revision as basis for packaging, if > you can. The tarballs are for systems where svn is not possible. The OpenBSD ports infrastructure doesn't support Subversion checkouts. Otherwise we would have to implement it for Subversion, git, mercurial, bzr, CVS... The result requires more work to mirror than a tarball. If the svn host provides some way to export tarballs from a revision or tag, they often don't provide stable checksums, or the URLs are temporal and not fetchable after a couple of days. Sometimes things are missing (e.g., Github does not include submodules in its tag-generated tarballs--something upstreams are often not aware of). Plus tarballs have PGP signatures I can check (if upstream provides them) and pregenerated configure scripts so I don't need to run automake or autoconf. And tarball mirrors are easy to scrape for updated versions (such as with portroach: http://www.openbsd.org/papers/eurobsdcon2015-portroach.pdf). I maintain a few dozen packages for OpenBSD; I do the best I can to keep them all up to date, but anything upstreams can do to make it easier to figure out what needs updating is greatly appreciated... so I'm very grateful for releases like the one Kevin just made. -- Anthony J. Bentley ------------------------------------------------------------------------------ _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
