Re: /bin/pwd

I'd like to come back to this (keeping changes only locally works, but
until now I've found no better solution than to have a patch, apply it
and always revert before making modifications, which is not nice.):

Jan Stary wrote:
> You are suggesting to discard the standard, portable way of doing things
> in order to accommodate one Frankenstein system.
> Not that I have any say in this, but no way.

What's more portable: /bin/pwd (which does not work on my
"Frankenstein system") or pwd (which works on my system, too)?

Or put differently: Is there any system that we know of where my
change actually breaks something?


As a side note:
> How about you locally make a /bin/pwd symlink
> and leave things like they should be?

This might work on my laptop, where I'm root and so on. But I might
also want to push the build (nix allows for that in a very convenient
way) to one random (low load) computer in my universities computer
pool.

> Hm, yet another Frankenstein. If you have a cp(1) that cannot cp
> or a mv(1) that cannot mv, fix _that_ before writing any scripts.

Yes, I fix it by providing my own ... in ~/bin.
One is not always root.


Another note: /bin/pwd will (does) break on a system with GNU Guix,
too. Guix is the (only?) package manager under the GNU umbrella.

------------------------------------------------------------------------------
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel