April 2012 - cabal-devel

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 22 Apr '12

22 Apr '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: assigned Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Changes (by ttuegel): * status: new => assigned Comment: Replying to [comment:9 tibbe]: > Replying to [comment:8 ttuegel]: > > Even with the patch I just attached, 'cabal configure' needs to be run first, but I doubt we want to change that behavior. > > I think we do! We already run configure automatically before build in most cases. I think we should always do that. That's a good point. I need to remake the patch for the new Git repo anyway; I'll make sure that's included. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:10> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

cabal repository moved to Github
by Andres Löh 22 Apr '12

22 Apr '12

Hi everyone. The cabal repository now lives at Github: https://github.com/haskell/cabal The bug tracker remains with Trac for now. I'll run some experiments with converters from Trac to Github to see whether it's feasible to convert that as well. The darcs repositories should no longer be used. Cheers, Andres -- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com

3 3

[Hackage] #944: Duplicate C symbol names
by Hackage 22 Apr '12

22 Apr '12

#944: Duplicate C symbol names -----------------------------+---------------------------------------------- Reporter: PaulVanDerWalt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.14.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: 7.2.2 Platform: Mac OS | -----------------------------+---------------------------------------------- I've run into a problem where I want to include the vty and haskeline packages, which both contain the same C code, of which the symbol names are not translated or made unique. When I use both packages, and try to compile something which has Template Haskell (which triggers loading of all dependencies), I get the following error. GHCi runtime linker: fatal error: I found a duplicate definition for symbol _mk_wcswidth whilst processing object file /Users/paul/.cabal/lib/haskeline-0.6.4.6/ghc-7.2.2/HShaskeline-0.6.4.6.o A workaround is to patch the libraries to make the function names unique, but this is less than ideal. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/944> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Cabal's detailed test interface
by Thomas Tuegel 22 Apr '12

22 Apr '12

Greetings interested Cabal users and developers! I am pleased to present another revision of Cabal's detailed test interface for your scrutiny. I have attached a patch for the Cabal repository to this message so you can try the new interface and test runner for yourselves, but the interface from Distribution.TestSuite is included below with a few of my comments. This interface is based very heavily on Duncan's proposal from our last round of discussion. I indicated deviations by comments in the source, but the commit log is a good summary of the changes: * The constructors of 'Tests' have been renamed. I think 'TestGroup' and 'ExtraTestOptions' are redundant: it is clear from context what sort of Group and what sort of ExtraOptions are being considered and qualified imports can resolve any name conflicts. Group and ExtraOptions have the advantage of improving the brevity of pattern matches on Tests, which are used very often in D.S.Test. * The 'concurrentSafe :: Bool' field of TestInstance has become the 'concurrently' field of Group, allowing package and test framework authors greater control over concurrency. * The 'Finished' constructor of 'Progress' now contains the options used to run the test in addition to the test result. Without returning the options, it would be difficult to extract the RNG seed used to run a test. * A detailed test suite module now exports the symbol 'test :: IO Tests'. This enables the use of IO to enumerate the tests in a group, suggested by Duncan as a way to accommodate the GHC test suite. > module Distribution.TestSuite > ( TestInstance(..) > , OptionDescr(..) > , OptionType(..) > , Tests(..) > , Options > , Progress(..) > , Result(..) > ) where > > data TestInstance = TestInstance > { run :: IO Progress -- ^ Perform the test. > , name :: String -- ^ A name for the test, unique within a > -- test suite. > , tags :: [String] -- ^ Users can select groups of tests by > -- their tags. > , options :: [OptionDescr] -- ^ Descriptions of the options recognized > -- by this test. > , setOption :: String -> String -> Either String TestInstance > -- ^ Try to set the named option to the given value. Returns an error > -- message if the option is not supported or the value could not be > -- correctly parsed; otherwise, a 'TestInstance' with the option set to > -- the given value is returned. > } > > data OptionDescr = OptionDescr > { optionName :: String > , optionDescription :: String -- ^ A human-readable description of the > -- option to guide the user setting it. > , optionType :: OptionType > , optionDefault :: Maybe String > } > deriving (Eq, Read, Show) > > data OptionType > = OptionFile > { optionFileMustExist :: Bool > , optionFileIsDir :: Bool > , optionFileExtensions :: [String] > } > | OptionString > { optionStringMultiline :: Bool > , optionStringDescription :: String > } > | OptionNumber > { optionNumberIsInt :: Bool > , optionNumberBounds :: (Maybe String, Maybe String) > } > | OptionBool > | OptionEnum [String] > | OptionSet [String] > | OptionRngSeed > deriving (Eq, Read, Show) > > data Tests > = Test TestInstance > | Group > { groupName :: String > , concurrently :: Bool -- ^ If true, then the child 'Test's or > -- 'Group's can safely be run concurrently; > -- otherwise, they must be run in series. > , groupTests :: [Tests] > } > | ExtraOptions [OptionDescr] Tests > > type Options = [(String, String)] > > data Progress = Finished Options Result > -- ^ The options used must be returned when the test is finished, > -- or it will not be possible to recreate tests taking a random > -- seed. > | Progress String (IO Progress) > > data Result = Pass > | Fail String > | Error String > deriving (Eq, Read, Show) As always, your comments are appreciated. Thanks! -- Thomas Tuegel

4 15

patch applied (cabal): "Fix doc comment for ghcOptSourcePathClear" and 11 others
by Duncan Coutts 22 Apr '12

22 Apr '12

Wed Mar 28 20:08:42 PDT 2012 Duncan Coutts <duncan(a)community.haskell.org> * Fix doc comment for ghcOptSourcePathClear Spotted by tibbe M ./Cabal/Distribution/Simple/Program/GHC.hs -1 +2 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Jul 26 15:29:23 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * New detailed test suite interface. This patch implements a new interface for detailed test suites based on Duncan's proposal. This implementation differs from his in a few ways: * The constructors of 'Tests' have been renamed. I think 'TestGroup' and 'ExtraTestOptions' are redundant: it is clear from context what sort of Group and what sort of ExtraOptions are being considered and qualified imports can resolve any name conflicts. Group and ExtraOptions have the advantage of improving the brevity of pattern matches on Tests, which are used very often in D.S.Test. * The 'concurrentSafe :: Bool' field of TestInstance has become the 'concurrently' field of Group, allowing package and test framework authors greater control over concurrency. * The 'Finished' constructor of 'Progress' now contains the options used to run the test in addition to the test result. Without returning the options, it would be difficult to extract the RNG seed used to run a test. * A detailed test suite module now exports the symbol 'test :: IO Tests'. This enables the use of IO to enumerate the tests in a group, suggested by Duncan as a way to accomodate the GHC test suite. M ./Cabal/Distribution/Simple/Test.hs -72 +152 M ./Cabal/Distribution/TestSuite.hs -259 +68 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Fri Jul 29 08:02:38 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Renamed Distribution.TestSuite.Tests to Test. M ./Cabal/Distribution/Simple/Test.hs -4 +4 M ./Cabal/Distribution/TestSuite.hs -4 +4 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Fri Jul 29 08:10:01 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Removed obsolete LANGUAGE pragma from Distribution.TestSuite. M ./Cabal/Distribution/TestSuite.hs -1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Fri Jul 29 08:42:49 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Cleaned for warnings in D.TestSuite and D.S.Test. M ./Cabal/Distribution/Simple/Test.hs -4 +4 M ./Cabal/Distribution/TestSuite.hs -1 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Fri Jul 29 08:48:12 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Removed 'optionStringDescription' from OptionType. M ./Cabal/Distribution/TestSuite.hs -1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Thu Sep 1 11:26:06 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Changed detailed test exported type to [Test]. M ./Cabal/Distribution/Simple/Test.hs -21 +23 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Sep 6 14:16:11 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Clean D.S.Test for unused symbols. The unused declarations were all related to replaying test suites with logged options, but the command-line option for this feature has been disabled for some time. Changing the detailed test suite type to expect "tests :: IO [Test]" instead of "tests :: IO Test" made the old method of replaying options clumsy. Since it was already disabled, I chose to remove it, rather than rewrite it again. M ./Cabal/Distribution/Simple/Test.hs -45 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Sep 6 14:55:57 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Removed Options from Finished. M ./Cabal/Distribution/Simple/Test.hs -3 +8 M ./Cabal/Distribution/TestSuite.hs -4 +1 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Sep 6 14:56:00 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Improved documentation for 'concurrently' field of Test. M ./Cabal/Distribution/TestSuite.hs -3 +8 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Sep 6 16:36:32 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Added 'testGroup' to D.S.TestSuite. M ./Cabal/Distribution/TestSuite.hs +6 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=… Tue Sep 6 16:49:31 PDT 2011 Thomas Tuegel <ttuegel(a)gmail.com> * Updated user manual for new detailed interface. M ./Cabal/doc/developing-packages.markdown -27 +21 View patch online: http://darcs.haskell.org/cgi-bin/darcsweb.cgi?r=cabal;a=darcs_commitdiff;h=…

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 22 Apr '12

22 Apr '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by tibbe): Replying to [comment:8 ttuegel]: > Even with the patch I just attached, 'cabal configure' needs to be run first, but I doubt we want to change that behavior. I think we do! We already run configure automatically before build in most cases. I think we should always do that. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:9> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 21 Apr '12

21 Apr '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by ttuegel): Even with the patch I just attached, 'cabal configure' needs to be run first, but I doubt we want to change that behavior. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Github migration of Cabal repo is problematic
by Andres Löh 21 Apr '12

21 Apr '12

Hi. I have converted the existing Cabal/cabal-install darcs repo plus branches into a git repo. Per Igloo's request, I have tried to use the same method that has already been used by ghc to mirror the Cabal darcs repo to git, so that hashes of commits stay stable. However, it turns out that the resulting repo has two invalid commits: $ git fsck error in commit 26ef89b1272a0d860d8c0c0b06e9a78270b179c6: invalid author/committer line - missing space before email error in commit cc2f67f98fbc246f010516c71722d5c3432e0a2b: invalid author/committer line - missing space before email dangling tag d50b3b58bbaac67412af0e1e197946599a627f0d dangling tag 070e971fa01b7801c51455f924522d2edd4408e5 dangling tag b21bf31fc1a95688c27d5e2bd04224802ee9d82c dangling tag 272c383a0dcaeeb8d774136bfd8b555ddcaa32c4 dangling tag 633c2bf039bbfa3fb66b204d358519d374cade22 dangling tag bb40c2dce611768b03600f6baea8b5b19f4a5da3 dangling tag 074186b4abe147ad74287ce9d674b5e29a1989f1 dangling tag b0ae0f70fe571cb89b126eb4b3132627a846d2ca dangling tag 15b05c2da997604e4bbcfb89a6587a13c9db3705 dangling tag b5b5bb276b6102a07ed8e6f6c5aa9d4ca607c039 dangling tag a3baffce1f42c2368f653eaecba95a2278df5928 dangling tag 8ce6b0314c3eeacd6352d48e295b6362082fb68c The presence of these commits prevents me from pushing to github. One of these two is in the trunk and also present in the already mirrored repository on Github. Ian tells me that they have convinced the Github people to manually upload the repo in the past. The question now is how to deal with this situation: * Should I ask the Github admins again to do some manual intervention? Are we happy that these two patches won't cause problems in the future? * Or: Should we fix the two patches by rewriting the author information, but as a consequence changing nearly all the commit hashes of the Cabal repo, causing a less smooth transition for everyone who has an already checked out ghc source tree? Cheers, Andres

3 3

Re: [Hackage] #517: make cabal install command support haddock options
by Hackage 21 Apr '12

21 Apr '12

#517: make cabal install command support haddock options ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: normal | Milestone: cabal-install-0.14.2 Component: cabal-install tool | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: | Platform: ---------------------------------+------------------------------------------ Changes (by kosmikus): * milestone: cabal-install-0.14 => cabal-install-0.14.2 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/517#comment:20> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #517: make cabal install command support haddock options
by Hackage 21 Apr '12

21 Apr '12

#517: make cabal install command support haddock options ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: reopened Priority: normal | Milestone: cabal-install-0.14 Component: cabal-install tool | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: | Platform: ---------------------------------+------------------------------------------ Comment(by kosmikus): I don't think it's currently possible to do this via the configuration file. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/517#comment:19> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0