Bravo, you knew Ritchie and that makes you a Unix veteran, but you do not know everything there is to know no matter how many names you drop, and I doubt you were programming before I was born because I go back to that same era. I started with Unix on the VAX and I've worked since with just about every flavor of *Nix except System 370. Whether one's shebang is classic perl or env, they are functionally the same, and lazy is not pejorative in the Perl world, since Wall cites laziness as a desirable virtue of a good programmer. He also cites hubris, but I have a problem with hubris, especially yours. Using env permits one to put Perl in the file system wherever he desires. There are problems with installing user bits in system directories in macOS because of the changes Apple is making in High Sierra. We are up to 10.13.4 in less that six months and with the last two point releases Apple has broken everything that came before 10.13, twice. This means a macOS user with an interest in Perl has at least two versions of Perl on the machine, perhaps more. I have more than two, and several in different LINUXs in VirtualBox. Using env in shebang takes away some of the pain of dealing with this. And because Apple has changed the compiler and the libraries twice in 4 months, many Perl modules that use XS are broken and will not compile. PDL is one of these. PDL is very important to me but getting it to work and proving that it is broken because of Apple's libraries has been a challenging exercise in debugging. You can download a binary version of PDL for macOS but it won't work because it was compiled for macOS before 10.13. So, you have to build it from source, except it won't build because the libraries shipped with Xcode are incompatible with some of PDL's dependencies that use XS code. To get PDL to build you must first download Perl, build and install it other than in the standard location and only then will PDL build. This took many hours of hacking to finally figure all this out. And GNU env is stupid because it does not behave in a shebang the way rtfm says it should. Did you read that Eric Raymond piece I cited on the rule of "least surprise?" Did you read his "The Cathedral and the Bazaar?" No? Too bad, you could still learn something, maybe. See, I can drop names too, except it's pointless with you. Thus, at this particular time, many Perls in macOS and in debian in order to compare the behavior of one against another to find the culprits. I'm sure you could care less about any of this but getting env to work in debian as it does in macOS is important to me, thus my question to the Monks. You, like so many suffering from the hubris bug and "I know everything about programming because I knew Richie and I was writing code before you were born" is just so much BS. If I can make env on debian work the way I want it to work, who the hell are you to criticize? That's what open-source is all about. If you don't like the way a program behaves, and the maintainers won't change it, you have the source and you can change it yourself. So, go channel Ritchie and butt out of this thread, since your input is less than useful.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.