
my prior email is about how the BREW folks are having a hard time using
cabal sandboxing to support providing brew formulae for things like pandoc
etc
On Fri, Nov 1, 2013 at 4:14 PM, Yuri de Wit
I quite like the approach taken by 'brew' where you can 'link' and 'unlink' executables to and from a specific folder in the path:
*brew install apple-gcc42
**brew link apple-gcc42 **brew unlink apple-gcc42 *
The installed package has the knowledge of what needs to be linked and unlinked to/from the path (btw, it is a path managed by brew in /usr/local/bin similar to .cabal/bin or Library/Haskell/bin) and it is quite easy to manage the path with it.
On Fri, Nov 1, 2013 at 5:49 PM, Bob Ippolito
wrote: symlinks are generally how this gets "solved" in practice.
On Friday, November 1, 2013, Carter Schonwald wrote:
This.
Actually the Mac brew folks are hitting this issue exactly. Subtlty being you want to be able to install bin and share assets both to a custom location. Unclear how to do that currently.
On Friday, November 1, 2013, Tom Ellis wrote:
On Fri, Nov 01, 2013 at 06:37:13PM +0000, Tom Ellis wrote:
On Fri, Nov 01, 2013 at 01:31:33PM -0500, Gregory Guthrie wrote:
"I could see myself inadvertently cabal-installing utilities (eg: newt, bnfc, etc...) in sandboxes on accident.
What is wrong with this?
My guess is that Rogan was suggesting they wouldn't appear on the PATH.
I wonder if some compromise is possible whereby the binary builds in the sandbox but is installed to some user-wide location on the PATH.
Tom
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe