>> And, let's be frank; Macs cater (wisely, perhaps) to >> a group of users who don't know about, or want to know about, $PATH. > > Only if you stick to Apple-approved stuff. MacPorts, despite tacit support > from Apple, is an outsider and ultimately can never really integrate > seamlessly. (See for another example the discussion about /etc/paths.d / > path_helper. And all the stuff about XCode in the FAQ and ProblemHotList.)
Can `perl -V` be parsed to find out where things will be for a given perl? Perhaps adding a parsing of this to your $PATH will help avoid manually typing fullpaths and be a one-time tweak of the $PATH. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
