[112798] trunk/dports/archivers/upx/Portfile

Ryan Schmidt ryandesign at macports.org
Fri Nov 1 13:48:56 PDT 2013


On Nov 1, 2013, at 15:47, Jeremy Lavergne <jeremy at lavergne.gotdns.org> wrote:

>> Yes. But perl5 provided the files. A port could depend on bin:perl:perl5 and be assured that, if for some reason /usr/bin/perl did not exist, then the perl5 port would be installed and it would then provide /opt/local/bin/perl. The difference with “port select” is that there is no port that would provide /opt/local/bin/perl so there is no way to declare a dependency on it that could be satisfied by a port.
> 
> So assuming someone updated perl5.18 to use the select portgroup, is it still not viable?
> 

If we remove the perl5 port and switch to users using “port select” to create the /opt/local/bin/perl symlink, then we cannot from any other port rely on /opt/local/bin/perl existing, just like we cannot from any other port rely on anything else that “port select” creates for any other port.



More information about the macports-dev mailing list