- cabal-devel - Haskell.org

Package logo's
by Bas van Dijk 24 Oct '11

24 Oct '11

Hi Duncan, Attached is the package logo patch I was working on. * Show optional package logo on package page If a package has a logo.svg or logo.png file (all lower-case) in their package root then that logo is shown on the package page. SVG takes preference over PNG. Currently logos are served using the existing PackageContents feature. We could use a dedicated resource like "package/:package/logo" but this works fine for now. Regards, Bas

3 8

patch applied (cabal): "Fix source repo subdir name after cabal->Cabal dir rename"
by Duncan Coutts 23 Oct '11

23 Oct '11

Sun Oct 23 14:44:25 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Fix source repo subdir name after cabal->Cabal dir rename M ./Cabal/Cabal.cabal -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Add a source package index cache to speed up reading"
by Duncan Coutts 23 Oct '11

23 Oct '11

Sun Oct 23 14:32:53 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Add a source package index cache to speed up reading e.g. about 3x faster for cabal info pkgname M ./cabal-install/Distribution/Client/IndexUtils.hs -51 +252 M ./cabal-install/Distribution/Client/Update.hs -1 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Add package checks for benchmarks" and 4 others
by Duncan Coutts 23 Oct '11

23 Oct '11

Wed Oct 12 13:16:04 PDT 2011 Johan Tibell <johan.tibell(a)gmail.com> * Add package checks for benchmarks Refactor duplicate names check to avoid having to manually write all O(n^2) possible collision cases between executables, test suites, and benchmarks. M ./Cabal/Distribution/PackageDescription/Check.hs -20 +56 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Thu Oct 13 15:56:15 PDT 2011 Johan Tibell <johan.tibell(a)gmail.com> * Implement 'cabal bench' command The only implement benchmark interface so far is exitcode-stdio-1.0, which forwards the output of the benchmark executable being run to the parent process' stdout/stderr. M ./Cabal/Cabal.cabal +1 M ./Cabal/Distribution/Simple.hs -2 +28 A ./Cabal/Distribution/Simple/Bench.hs M ./Cabal/Distribution/Simple/InstallDirs.hs -1 +4 M ./Cabal/Distribution/Simple/Setup.hs +62 M ./Cabal/Distribution/Simple/UserHooks.hs -3 +14 M ./Cabal/Distribution/Simple/Utils.hs +10 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Thu Oct 13 16:21:09 PDT 2011 Johan Tibell <johan.tibell(a)gmail.com> * Add unit test for 'cabal bench' command-line flags A ./Cabal/tests/PackageTests/BenchmarkOptions/ A ./Cabal/tests/PackageTests/BenchmarkOptions/BenchmarkOptions.cabal A ./Cabal/tests/PackageTests/BenchmarkOptions/Check.hs A ./Cabal/tests/PackageTests/BenchmarkOptions/Setup.hs A ./Cabal/tests/PackageTests/BenchmarkOptions/test-BenchmarkOptions.hs M ./Cabal/tests/PackageTests/PackageTester.hs -1 +15 M ./Cabal/tests/suite.hs -2 +4 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Thu Oct 13 16:28:47 PDT 2011 Johan Tibell <johan.tibell(a)gmail.com> * Fail gracefully if 'cabal bench' is run before 'cabal build' M ./Cabal/Distribution/Simple/Bench.hs +7 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Sun Oct 23 14:39:24 PDT 2011 Duncan Coutts <duncan(a)community.haskell.org> * Bump versions of Cabal and cabal-install Latest cabal-install requires latest Cabal due to api addition M ./Cabal/Cabal.cabal -1 +1 M ./cabal-install/cabal-install.cabal -2 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Uploading build reports shouldn't fail if there are no reports"
by Duncan Coutts 23 Oct '11

23 Oct '11

Sun Oct 16 07:38:19 PDT 2011 Max Bolingbroke <batterseapower(a)hotmail.com> * Uploading build reports shouldn't fail if there are no reports M ./cabal-install/Distribution/Client/Upload.hs -11 +14 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Allow Haddock to be configured from the 'install' command" and 1 others
by Duncan Coutts 23 Oct '11

23 Oct '11

Sat Oct 15 10:01:01 PDT 2011 Max Bolingbroke <batterseapower(a)hotmail.com> * Allow Haddock to be configured from the 'install' command M ./cabal-install/Distribution/Client/Install.hs -12 +14 M ./cabal-install/Distribution/Client/Setup.hs -10 +28 M ./cabal-install/Main.hs -7 +7 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Sun Oct 16 04:08:52 PDT 2011 Max Bolingbroke <batterseapower(a)hotmail.com> * Add a (substituted) flag to allow configuration of Haddock's --use-contents flag M ./Cabal/Distribution/Simple/Haddock.hs -6 +14 M ./Cabal/Distribution/Simple/InstallDirs.hs +1 M ./Cabal/Distribution/Simple/Setup.hs +11 M ./cabal-install/Distribution/Client/Setup.hs -1 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (cabal): "Rename the cabal directory to Cabal"
by Ian Lynagh 23 Oct '11

23 Oct '11

Sun Oct 23 08:10:02 PDT 2011 Ian Lynagh <igloo(a)earth.li> * Rename the cabal directory to Cabal Makes things a little simpler in GHC's build system if libraries are in the same directory as their name. ./cabal -> ./Cabal M ./README -1 +1 M ./ghc-packages -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

patch applied (hackage-server): "Update dependencies so that it builds on ghc-7.2.1" and 2 others
by duncan＠lun.haskell.org 23 Oct '11

23 Oct '11

Thu Oct 20 21:36:13 BST 2011 Bas van Dijk <v.dijk.bas(a)gmail.com> * Update dependencies so that it builds on ghc-7.2.1 Ignore-this: b23effb8571e3de4d3310e37a2c5b81f It also requires a patched rss which is not yet released M ./Distribution/Server/Pages/Recent.hs -7 +3 M ./hackage-server.cabal -5 +5 Sun Oct 23 14:03:57 BST 2011 Duncan Coutts <duncan(a)well-typed.com> * Drop dependency on old-time Ignore-this: 5f59217f285c83117fa3f6d3e11bdd46 M ./Distribution/Server/Pages/Recent.hs -2 +1 M ./hackage-server.cabal -3 Sun Oct 23 14:05:04 BST 2011 Duncan Coutts <duncan(a)well-typed.com> * Allow building with older containers and deepseq Ignore-this: 837646be45f1000f2f8c8a8cc5e07f90 So it builds ok with the versions that come with ghc-6.12 and 7.0 M ./hackage-server.cabal -2 +15

1 0

patch applied (/home/srv/code/hackage-server): "crypt is not thread-safe so synchronize acces to it using a lock (MVar ())."
by duncan＠lun.haskell.org 22 Oct '11

22 Oct '11

Sat Oct 22 14:36:25 BST 2011 Bas van Dijk <v.dijk.bas(a)gmail.com> * crypt is not thread-safe so synchronize acces to it using a lock (MVar ()). Ignore-this: f322b7b456cd0db8d146397252a8e979 M ./Distribution/Server/Framework/AuthCrypt.hs -1 +7

1 0

Cabal plugins
by Antoine Latter 21 Oct '11

21 Oct '11

On Fri, Oct 21, 2011 at 3:49 PM, Jason Dagit <dagitj(a)gmail.com> wrote: > On Fri, Oct 21, 2011 at 1:29 PM, Brent Yorgey <byorgey(a)seas.upenn.edu> wrote: >> Hi everyone, >> >> I'm working on some improvements to 'cabal init', the biggest of which >> is looking at imports in source files to guess an initial list of >> dependencies to populate the 'Build-depends:' field. I wanted to get >> some feedback on a design decision: what to do when we find multiple >> packages providing the same module? > > While cabal init is something I use, I would prefer to have a separate > tool for calculating my build-depends field. Something that could > suggest things for an existing cabal project, ideally. Then I could > run that regularly during development to help me determine what my > build-deps should be and cabal init could suggest I run it (or run it > for me). > > While I'm suggesting features I would like, wouldn't it be great if > cabal used the plugin RFC that Simon came up with? > http://www.mail-archive.com/haskell-cafe@haskell.org/msg92770.html > > I think that interface is a great way to unify the tools that have > sprung up around cabal such as cabal-dev and cab. > One thing that will be hard for plugins is that there's no way to get at the package hooks without entering through Setup.main. This means that if your plugin wants to, say, call haddock with slightly tweaked arguments, you might miss something important that the standard 'cabal haddock' would have gotten because it runs the user hooks. (This concern only applies if your plugin is using the Cabal library to open up the package description and root around and do things). There's probably still a lot you can do, though - something like 'cabal-dev' could be entirely written as a plugin (and I guess it would be out-of-the-box: 'cabal dev configure' would 'just work' under this proposal, although the help text would need to change). Antoine

1 0