automatic "port select" after installing the first port in the group
egall at gwmail.gwu.edu
Mon Apr 7 05:41:16 PDT 2014
Sounds kind of like the "sensible alternatives" approach that many
dpkg-based package managers take:
On Mon, Apr 7, 2014 at 8:02 AM, Mojca Miklavec <mojca at macports.org> wrote:
> for Python ports it makes sense not to install "python" to $prefix/bin
> because that would shadow the python which comes with the system.
> What about if we currently ship a certain port that installs the
> binary to $prefix/bin and would like to allow parallel installation of
> a newer (experimental) version. In order to prevent conflicts the
> binaries should no longer end up in $prefix/bin. But would it be
> possible/allowed to automatically run "port select <port_group_name>
> <port_version>" after the first of two ports gets installed?
> That way the users would still get the expected binary in $prefix/bin
> when they first install the port. Those who want to play with both
> versions would still be free to do so by running "port select"
> manually at any time.
> macports-dev mailing list
> macports-dev at lists.macosforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev