On Jun 4, 2015, at 8:16 AM, René J.V. Bertin wrote: > On Thursday June 04 2015 07:23:24 Ryan Schmidt wrote: > >> depends_skip_archcheck is not a new type of dependency. >> depends_skip_archcheck does not declare a dependency. Rather, it specifies >> that an existing dependency does not need to have its architectures >> verified. So if you want to declare a build dependency on python27 and that >> architectures don't matter, you would write (untested): >> >> depends_build-append port:python27 >> depends_skip_archcheck-append python27 > > That's not how I have used the keyword; I've used it to declare a dependency > not declared in any other way, and that just worked as far as I can tell. > Maybe there's a check that adds an implicit depends_lib when adding a new > dependency through depends_skip_archcheck?
I can't reproduce that. Can you give an example of where that's been done? > >> Yes, one could modify the python ports to have the interpreter in a separate >> subport from the libraries. > > I think that'd be counterproductive; I agree. > as Joshua points out you cannot avoid having a universal interpreter (or its > entry point). I don't know what you'd be using it for (interactively, I mean; > using the same MacPorts tree on a 32bit and a 64bit VM perhaps?), but that is > not actually different from any other application. > No, what I had in mind is provide a way to refer to the interpreter that does > not take the architecture into account. I don't follow. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
