On Feb 21 22:02:19, dl...@geeklair.net wrote:
> On Feb 21, 2013, at 6:19 PM, Bruce R Miller <bruce.mil...@nist.gov> wrote:
> > But a "plain perl" used from commands like
> > perl Makefile.PL
> > will use the more common installation directories,
> > like macports used to do, and every other OS does.
It does now, doesn't it? Running 'perl whatever'
just picks the first 'perl' in your PATH.
> which just exchanges the specific behavior you don't want
> for a different broken behavior (think about what happens
> if/when you upgrade your macports perl but you have something
> in ${prefix}/bin that you installed locally that is now
> missing components...)
If the user installed something manually into $prefix/bin
that depends on a particular perl version (from macports),
and then upgraded that perl version via macports, and it
broke his manual $prefix/bin/stuff, it's the user's
own footshooting. It's none of macports bussines
to even care whether upgrading a macports version
of something breaks some none-macports software.
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
