[MacPorts] #41796: binary package download ignores macosx_deployment_target set globally
MacPorts
noreply at macports.org
Mon Dec 16 13:49:27 PST 2013
#41796: binary package download ignores macosx_deployment_target set globally
------------------------+--------------------------------
Reporter: william@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.2.1
Resolution: | Keywords:
Port: |
------------------------+--------------------------------
Comment (by ryandesign@…):
Replying to [comment:6 william@…]:
> > The reason it was added as a global option is because it was requested
in #19875. However it was never advertised or documented and remains an
unsupported option for now. This capability is not in high demand.
>
> It is documented in “man portfile” without that caveat, thus:
>
> {{{
> macosx_deployment_target
> Value for MACOSX_DEPLOYMENT_TARGET environment variable when
invoking the configure script.
> Type: optional
> Default: (current OS version)
> Example:
> macosx_deployment_target 10.4
> }}}
"man portfile" documents things that can be done in a portfile, not things
that can be done in macports.conf. The caveat I mentioned above applies to
the global option, not to the portfile option; the portfile option is
supported and works as intended.
> Is it possible to get something added to http://guide.macports.org/
and/or the man pages for port / portfile / macports.conf to mention this
as a way to help others out in the future? At the moment I see:
>
> {{{
> configure.macosx_deployment_target, configure.macosx_deployment_target-
append, configure.macosx_deployment_target-delete
>
> TODO: add description
>
> Default: ???
>
> Example:
>
> TODO: add example
> }}}
That part of the documentation is out of date. The portfile option was
briefly called "configure.macosx_deployment_target" before being changed
to just "macosx_deployment_target" several years ago. This section
documents (or fails to document) the portfile option, not the global
option.
> I guess this knowledge should either appear in the “buildfromsource”
section of the documentation, or in that for each of the variables which
can cause problems of this type when non-default.
In fact the documentation barely mentions that we have pre-compiled
binaries at all, and could really use some work.
--
Ticket URL: <https://trac.macports.org/ticket/41796#comment:7>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list