February 2011 - cabal-devel

patch applied (cabal-install): Remove unnecessary Maybe from LocalUnpackedPackage dir filepath
by Duncan Coutts 13 Feb '11

13 Feb '11

Sun Feb 13 08:51:51 PST 2011 Duncan Coutts <duncan(a)community.haskell.org> * Remove unnecessary Maybe from LocalUnpackedPackage dir filepath We can just use "." instead of Nothing M ./Distribution/Client/Configure.hs -1 +1 M ./Distribution/Client/Install.hs -2 +2 M ./Distribution/Client/Types.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

patch applied (cabal-install): Change the interface of the two package index search functions
by Duncan Coutts 13 Feb '11

13 Feb '11

Sun Jan 23 11:37:06 PST 2011 Duncan Coutts <duncan(a)community.haskell.org> * Change the interface of the two package index search functions Move the ambiguity checking to the only use site Both normal and substring search now return [(PackageName, [pkg])] M ./Distribution/Client/IndexUtils.hs -7 +17 M ./Distribution/Client/List.hs -3 +8 M ./Distribution/Client/PackageIndex.hs -16 +15 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

patch applied (cabal-install): cabal report uses the correct URIs and authenticates with username and passwords flags
by Duncan Coutts 13 Feb '11

13 Feb '11

Mon Nov 8 10:49:27 PST 2010 Vo Minh Thu <noteed(a)gmail.com> * cabal report uses the correct URIs and authenticates with username and passwords flags M ./Distribution/Client/BuildReports/Upload.hs -8 +11 M ./Distribution/Client/Config.hs -4 +17 M ./Distribution/Client/Setup.hs -6 +52 M ./Distribution/Client/Upload.hs -20 +33 M ./Main.hs -3 +7 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

patch applied (cabal-install): Change position of --only-dependencies in --help listing
by Duncan Coutts 13 Feb '11

13 Feb '11

Sun Feb 13 09:19:56 PST 2011 Duncan Coutts <duncan(a)community.haskell.org> * Change position of --only-dependencies in --help listing Move it next to the --upgrade-dependencies flag M ./Distribution/Client/Setup.hs -6 +7 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

patch applied (cabal-install): Add an --only-dependencies flag to "install" (see ticket #697)
by Duncan Coutts 13 Feb '11

13 Feb '11

Wed Jun 30 14:37:36 PDT 2010 josh.hoyt(a)galois.com * Add an --only-dependencies flag to "install" (see ticket #697) This flag installs only the dependencies of the packages that were explicitly mentioned on the command line. This is useful for using cabal-install in development environments, where the developer needs the dependencies to build the package in development, but does not yet want to install the package itself. M ./Distribution/Client/Install.hs -8 +36 M ./Distribution/Client/InstallPlan.hs +15 M ./Distribution/Client/Setup.hs +10 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

Re: [Hackage] #402: Automatic hoogle database for installed packages
by Hackage 13 Feb '11

13 Feb '11

#402: Automatic hoogle database for installed packages ---------------------------------+------------------------------------------ Reporter: Peaker | Owner: dschoepe Type: enhancement | Status: assigned Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Comment(by duncan): I applied the other patch about generating hoogle and html output in one go. I've looked at this patch but I think it needs a bit more thought. So, the general idea is to create a binary .hoo file for each package right? Generating a merged binary database would be a separate task, not covered by this patch. There are two issues: 1. The code in the doc step of cabal-install is assuming a certain layout of the build tree by reading and writing files directly in the build tree. This will not work for packages using build-type custom. It would be ok if we were copying into a temporary image dir before doing the real installation. In that case writing extra files into the temporary image dir would be fine. As it is, I think this feature of generating a per- package .hoo db would be better in the build system itself, in the Cabal lib. 2. according to the [http://www.haskell.org/haskellwiki/Hoogle#Database_Creation hoogle manual], the .hoo files of dependencies need to be specified as well. Since each .txt can be converted into a .hoo, and the final .hoo is not really useful except as something to use to merge into a db that users will actually use, perhaps it would be better to just generate the .txt files per-package and then generate a big merged one. Alternatively, why generate the .txt files if we could just generate the .hoo files? Is there any point in generating both .txt and .hoo files for each package? More minor comments about the patch. It should use the existing framework for running programs. This would cut down on the code and integrate it properly with the Cabal exception handling and logging stuff. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/402#comment:7> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

patch applied (cabal-install): Change my email address
by Duncan Coutts 13 Feb '11

13 Feb '11

Sun Jan 23 12:21:00 PST 2011 Duncan Coutts <duncan(a)community.haskell.org> * Change my email address M ./Distribution/Client/Dependency/TopDown/Constraints.hs -1 +1 M ./Distribution/Client/IndexUtils.hs -1 +1 M ./Distribution/Client/InstallPlan.hs -1 +1 M ./Distribution/Client/Tar.hs -1 +1 M ./cabal-install.cabal -2 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

patch applied (cabal-install): fix a comment typo of 'according'
by Duncan Coutts 13 Feb '11

13 Feb '11

Sat Jan 22 05:53:39 PST 2011 Jens Petersen <petersen(a)haskell.org> * fix a comment typo of 'according' M ./Distribution/Client/Dependency/TopDown.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal-install;a=darcs_commi…

1 0

Re: [Hackage] #645: confusing interface: cabal "install" subcommand has two clashing meanings
by Hackage 11 Feb '11

11 Feb '11

#645: confusing interface: cabal "install" subcommand has two clashing meanings ---------------------------------+------------------------------------------ Reporter: StefanK | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by duncan): See also #802 about consequences of people using `cabal copy` instead of `cabal install`. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/645#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Haskell-cafe] [Cabal-devel] Cabal && license combinations
by Antoine Latter 10 Feb '11

10 Feb '11

On Thu, Feb 10, 2011 at 10:04 AM, Chris Smith <cdsmith(a)gmail.com> wrote: > On Thu, 2011-02-10 at 08:59 +0100, Ketil Malde wrote: >> I disagree - the linked executable must, but not the wrapper by itself. >> It's source code, i.e. text, thus a creative work, and therefore >> covered by copyright - on its own. > > You're certainly right from a legal standpoint. But being right doesn't > actually matter. The instant anyone actually compiles an application > that uses your library, however indirectly, they are bound by the terms > of the underlying library as well. So your bindings are effectively > covered by the underlying license anyway (unless you're choosing a > license for the sake of people who will never produce any usable end > result...) > The vast majority of Open Source licenses in use only restrict the publication of the work or derived works, not compilation. So no, the instant of compilation is not when the transitive dependencies kick in, it is the publication of compiled binaries, which in my mind is a pretty specialized case. Antoine

2 1