Re: Problem building/packaging 1.8.0 swig bindings
From: Daniel J. Luke <dluke_at_geeklair.net>
Date: Fri, 12 Jul 2013 19:16:44 -0400
On Jul 12, 2013, at 5:38 PM, Daniel Shahaf <danielsh_at_elego.de> wrote:
For MacPorts I want to avoid having to have anyone installing the port have to run autogen (so I don't have to add dependencies on swig/python/autotools to each of the swig bindings ports). We've also got a strong preference towards tarballs because of some benefits that don't exist for builds that come from a source control system (they can be mirrored by the macports infrastructure, we do checksums on them to make sure they're the same file that the port was written for, we get repeatable builds as the tarball isn't going to change without us noticing while someone could repoint the tag on us...).
-- Daniel J. Luke +========================================================+ | *---------------- dluke_at_geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+Received on 2013-07-13 01:17:23 CEST |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.