On Feb 21, 2013, at 12:30 PM, Bruce Miller <[email protected]> wrote:
>> yes. What I'm saying is if you do ${prefix}/bin/perl Makefile.PL && make &&
>> make install you're installing something into MacPorts' ${prefix} that
>> MacPorts doesn't know about - it's much better to use 'port' to manage
>> installs and whatnot for ${prefix}
>
> Well, I don't quite say that: My instructions for users that want
> to mess with svn checkout is simply
> perl Makefile.PL
> make
> (sudo) make install
>
> Under normal circumstances they'd be getting "the" perl
> (with macports, presumably the one isntalled in /opt/local/bin ?)
>
> So, it seems that $prefix IS the one that macports should know about.
yes, you are telling your users to install stuff into ${prefix} without using
the 'port' command. This means they are installing files that MacPorts doesn't
know about.
--
Daniel J. Luke
+========================================================+
| *---------------- [email protected] ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
