Stop! Tickets are now managed at GitHub.

Please enter new tickets, and find and edit existing tickets there:

Ticket #113 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Haskell Platform for OS X does not run postflight script

Reported by: kballard Owned by: MtnViewMark
Priority: major Milestone: 2011.4.0.0
Component: OSX installer Keywords:


The OS X installer for the Haskell Platform is supposed to run a postflight script that symlinks the binaries from /Library/Frameworks/HaskellPlatform.framework/bin into /usr/local/bin. This postflight script does not actually appear to get run (or if it does get run then it doesn't have the proper permissions to actually work). Instead it gets installed at /Library/Frameworks/HaskellPlatform.framework/scripts/postflight.

Change History

Changed 4 years ago by kballard

In my particular case, after installing the platform and logging out/back in (as required by the installer, see ticket #112), my /usr/local/bin folder had not changed. It contained symlinks to alex and happy and a copy of the old cabal 0.6.2 from my previous install of the haskell platform. Running sudo /Library/Frameworks/HaskellPlatform.framework/scripts/postflight fixed the problem.

Changed 4 years ago by kballard

Turns out the scripts/postflight file doesn't actually get installed, it was left over from my previous installation of the Haskell Platform. The current installer simply never symlinks the binaries into /usr/local/bin like it should.

Changed 4 years ago by gregorycollins

  • status changed from new to assigned

Thanks for the bug report, this should be fixed in the next beta release (probably this weekend.)

Changed 3 years ago by MtnViewMark

  • owner changed from gregorycollins to MtnViewMark
  • status changed from assigned to new

Changed 3 years ago by MtnViewMark

  • status changed from new to closed
  • resolution set to fixed
  • milestone set to 2011.x.0.0

fixed, though they are symlinked into /usr/bin, as that is where the GHC postflight links things

Note: See TracTickets for help on using tickets.