March 2008 - cabal-devel

patch applied (cabal-install): In 'list', also include packages that are only installed and not available
by Duncan Coutts 02 Mar '08

02 Mar '08

Sun Mar 2 17:03:46 PST 2008 Duncan Coutts <duncan(a)haskell.org> * In 'list', also include packages that are only installed and not available Previously we took the available packages and did an inner join with the installed packages so we missed out packages like base which are installed by not available. Now we get the selected installed and available package sets and do a full outer join using a sort and merge operation. Also use a proper data type to hold the info we print about each package. M ./Hackage/List.hs -92 +142 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080303010346-adfee-…

1 0

patch applied (cabal-install): Remove shortopt -I for --installed
by Duncan Coutts 02 Mar '08

02 Mar '08

Sun Mar 2 11:56:39 PST 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Remove shortopt -I for --installed M ./Hackage/Setup.hs -1 +1 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080302195639-fdf66-…

1 0

patch applied (cabal-install): Implement 'cabal list --simple-output'
by Duncan Coutts 02 Mar '08

02 Mar '08

Sun Mar 2 11:54:37 PST 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Implement 'cabal list --simple-output' Provides a output format that is easier to pass on to unix tools and other scripting tools. Also works together with --installed. M ./Hackage/List.hs -9 +29 M ./Hackage/Setup.hs -2 +10 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080302195437-fdf66-…

1 0

using haddock markup in Description field
by Henning Thielemann 02 Mar '08

02 Mar '08

I like to use Haddock markup like bird track (>) and enumerations (*) in the Description field of a package. However I can't get it working, the mentioned markup is simply ignored. The content of the description field must be indented, is it unindented before passing to Haddock?

2 3

patch applied (cabal-install): Implement --installed to 'cabal list'
by Duncan Coutts 02 Mar '08

02 Mar '08

Sat Mar 1 14:27:04 PST 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Implement --installed to 'cabal list' Adding --installed to 'cabal list' will make it print only packages that are installed. M ./Hackage/List.hs -10 +25 M ./Hackage/Setup.hs -11 +42 M ./Main.hs -4 +10 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080301222704-fdf66-…

1 0

patch applied (cabal-install): Improve 'cabal list'
by Duncan Coutts 02 Mar '08

02 Mar '08

Sat Mar 1 12:21:17 PST 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Improve 'cabal list' Make the output of 'cabal list' prettier. $ cabal list xmonad * xmonad Latest version available: 0.6 Latest installed version: 0.6 Homepage: http://xmonad.org Category: System Synopsis: A tiling window manager License: BSD3 * xmonad-contrib ...[snip] Very much like the gentoo tools eix and esearch. This targets part of ticket #235. It still does not show packages that are installed but not available. M ./Hackage/List.hs -18 +58 M ./Main.hs -1 +3 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20080301202117-fdf66-…

1 0

darcs patch: Try to replace the index file atomically.
by Duncan Coutts 02 Mar '08

02 Mar '08

This is only locally tested in a copy of the archive. Sun Mar 2 19:42:01 GMT 2008 Duncan Coutts <duncan(a)haskell.org> * Try to replace the index file atomically. Using gzip > file means the file is created/replaced at the begining of the procedure, so for the period until it finishes the index file is in fact invalid. So re-generate the index into a temp file and then atomically rename. This does not make the regeneration totally atomic since while it is being generated, other files could be being added to the archive. BTW, could we set the 'darcs send' email address for the hackage-scripts repo so it works automagically. Would it also make sense for changes in the hackage-scripts to be sent to cabal-devel, like for the Cabal and cabal-install repos? Duncan

1 0

darcs patch: Improve 'cabal list' (and 1 more)
by Lennart Kolmodin 02 Mar '08

02 Mar '08

Sat Mar 1 21:21:17 CET 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Improve 'cabal list' Make the output of 'cabal list' prettier. $ cabal list xmonad * xmonad Latest version available: 0.6 Latest installed version: 0.6 Homepage: http://xmonad.org Category: System Synopsis: A tiling window manager License: BSD3 * xmonad-contrib ...[snip] Very much like the gentoo tools eix and esearch. This targets part of ticket #235. It still does not show packages that are installed but not available. Sat Mar 1 23:27:04 CET 2008 Lennart Kolmodin <kolmodin(a)gentoo.org> * Implement --installed to 'cabal list' Adding --installed to 'cabal list' will make it print only packages that are installed.

1 0

every use of BSD4 on hackage is incorrect
by Duncan Coutts 01 Mar '08

01 Mar '08

The following hackage packages specify in their .cabal file: license: BSD4 Which is the 4-clause BSD license, ie the one with the advertising clause. cabal-upload-0.3 Chart-0.5 FiniteMap-0.1 haxr-3000.0.1 haxr-th-1.0 hbeat-0.1 htar-0.1 pcap-0.4.2 tar-0.1.1.1 unix-compat-0.1.2.1 Inspecting the LICENSE files for every one of these packages reveals that they actually use the 3-clause BSD license. Not a single hackage package really uses the 4-clause BSD license. In every case that it has been used it was just a confusion. We therefore propose to deprecate BSD4 as a valid license in .cabal files: http://hackage.haskell.org/trac/hackage/ticket/205 In the unlikely case that anyone really wants to use the 4-clause BSD license they can still specify "license: OtherLicense" and put the text in the accompanying LICENSE file. Additionally, I propose to add the MIT license since there are a couple packages that really use that and allow optional versions on the licenses that are versioned, which includes the GPL and LGPL. Looking at OtherLicense we find common ones are MIT, variations on BSD3 (2 clause and fewer, other informal variations), disjunctions of BSD3 / GPL (ie dual licensing), conjunctions of BSD3 / GPL (ie some bits user BSD some under GPL). Duncan

2 1

Re: every use of BSD4 on hackage is incorrect
by Duncan Coutts 01 Mar '08

01 Mar '08

On Sat, 2008-03-01 at 10:39 +0100, Felix Martini wrote: > Right now i cannot see a reason why the cabal license field is an > enumeration instead of a string. The purpose seems to be to direct > people to preferred licenses of the Haskell community. If so this is > the wrong approach imo. It's not clear that that is the intention. This has been in the spec and the design since the very beginning. You'd have to ask someone who helped with the original spec to be sure of the intention. http://haskell.org/cabal/release/old/users-guide-0.1/x29.html#pkg-descr http://haskell.org/cabal/release/cabal-1.0/doc/pkg-spec-html/ It has always allowed for using any license. I suspect the intention was for convenience and to provide some consistency for common licenses, eg so we don't get packages specifying "gpl", "gpl2" "gpl-2" "GPL" and we have to wonder if those are all the same. In the common case it gives machine recognisable information. Duncan

1 0