> On 7 May 2015, at 5:48 pm, petr <[email protected]> wrote:
>
>
> Hi all,
>
> I am working on some new port. It works already quite fine, but I observe
> that when using it without Tracemode, it would pick up various already
> installed programs. Most of these are also provided by Xcode, but notably
> when `doxygen` is picked up, it also creates some extra documentation. This
> all works smoothly, but it would not create a consistent build across various
> installs. Is there a canonical way to avoid such problems?
If these dependencies add additional useful featured, then why not just make
your port depend on the MacPorts versions of them (assuming they exist of
course). Then you get the repeatable builds as well as those added features.
Better yet, make those dependencies something that can be turned on and off via
variants (particularly if the dependencies list is long such that you might not
want them by default). Then users can decide. Of course, this also requires the
ability to turn off support in your port. This is something that depends on the
build system your port uses, and what options that has to do this.
Chris
>
> Thanks!
> ~petr
>
> _______________________________________________
> macports-dev mailing list
> [email protected]
> https://lists.macosforge.org/mailman/listinfo/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
