On Saturday 07 August 2010 16:13:08 m...@svn.gobolinux.org wrote:
> Author: mwh
> Date: 2010-08-06 21:13:08 -0700 (Fri, 06 Aug 2010)
> New Revision: 4366
>
> Modified:
> trunk/Scripts/bin/Alien-Cabal
> Log:
> Remove debugging log that makes Cabal unportable
>
> Modified: trunk/Scripts/bin/Alien-Cabal
> ===================================================================
> --- trunk/Scripts/bin/Alien-Cabal 2010-07-30 21:32:14 UTC (rev 4365)
> +++ trunk/Scripts/bin/Alien-Cabal 2010-08-07 04:13:08 UTC (rev 4366)
> @@ -59,9 +59,9 @@
> alien_cabal--install() {
> if [ -z "$2" ]
> then
> - cabal install --global "$1" >>/Users/kquick/cabal.log
> + cabal install --global "$1"
> else
> - cabal install --global "$1-$2" >>/Users/kquick/cabal.log
> + cabal install --global "$1-$2"
> fi
> }
In fact, following up on this further, it seems that Alien-Cabal doesn't ever
work at all. All it does is spew files all over the filesystem through
/usr/local. And it can't install anything until you run `sudo cabal update`
manually, which writes to /Users/root/.cabal.I don't really understand how the Cabal-Install recipe is working, but something along the lines of how it makes things go in the right place needs to happen for Alien-Cabal too. At the moment it just isn't useful, but at least it fails early because of the bug fixed in this commit. I may revert it before any coming release so users aren't exposed to that contamination potential. -Michael
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
