Re:Why inbreeding is bad for your community
by jmillikin on Sunday October 28, 2012 @02:10PM
(#4709535)
In my experience, other package managers (my experience is with Python's and Ruby's) will behave just like Haskell's. Specifically, they do not seem to inspect the user's $PATH variable to determine whether their default installation directory is present.
Re:Why inbreeding is bad for your community
by wowzer on Sunday October 28, 2012 @02:51PM
(#4709633)
Having used both Haskell's package manager cabal and Python's pip and easy_install. Cabal has a long way to go before it's anything like pip. You can see cabal moving in the right direction, but pip is leagues ahead of it right now, especially when using virtualenv.
Re:Why inbreeding is bad for your community
by jmillikin on Sunday October 28, 2012 @03:26PM
(#4709725)
In what ways do you find pip better than cabal, or pip+virtualenv better than cabal-dev?
Re:Why inbreeding is bad for your community
by carterschonwald on Sunday October 28, 2012 @02:35PM
(#4709590)
I agree with everything you have posted.
>Please name one package manager which installs binaries to the user's home directory, but doesn't require updating the user's $PATH.
Do you even realize how little those two statements follow each other? The whole red herring argument here is kind of annoying, but I'll hit it anyways- every package manager that I've used which installs binaries (or anything, really) in the user's home directory (or any directory really) does make me update the path- but it also tells me this and gives me sane errors when that hasn't happened.