Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 19b52003 | 2015-09-21 18:29:02 | Set MODGHC_PACKAGE_KEY and adjust plist. | ||
| 1045085e | 2014-12-08 09:15:01 | Update plists and bump. | ||
| be7ce949 | 2013-01-20 17:56:05 | Regenerate plist for profiling libs. | ||
| 2acb3c83 | 2012-10-28 23:24:28 | Move the @exec and @unexec lines running the {,un}register.sh scripts and the line with the unregister.sh script down to the bottom of the plist. Silences all the blurb about ".../*.haddock doesn't exist or isn't a file." | ||
| 5a10eaa1 | 2011-12-05 14:56:30 | Updates: HDBC-2.3.1.0 HDBC-mysql-0.6.5.1 HDBC-sqlite3-2.3.3.0 | ||
| 68bcd200 | 2011-04-11 14:33:07 | Bump after ghc update. | ||
| 7d9a1039 | 2010-10-28 13:51:00 | - regen plist after recent ghc.port.mk change - adjust @exec/@unexec accordingly "just go ahead" kili@ | ||
| bcea0ad2 | 2010-05-19 15:58:18 | Silent register.sh/unregister.sh after the change to Cabal in ghc. Run unregister.sh with `--force'. | ||
| d73ffa85 | 2010-05-14 09:08:25 | Use @unexec. I must have been on drugs when using @unexec-delete for unregister.sh in all the new ghc libraries (which leads to bogus registered ghc packages after updates). You can use the command ghc-pkg check to check ghcs internal package list. If it reports missing files for some package (like hashed-storage-0.4.11), you can forcibly unregister it by running (as root) something like ghc-pkg unregister hashed-storage-0.4.11 ok dcoppa@ | ||
| be134e54 | 2010-04-15 14:24:47 | Import hs-HDBC-sqlite3, the Sqlite v3 driver for HDBC. Not yet wired to the build. OK kili@ |