be friendlier to user (was Re: What's next?)
On Wed, 4 Sep 2013 21:14:03 -0700 Johan Tibell johan.tib...@gmail.com wrote: Hi all, With 1.18 out the door it's time to look towards the future. Here are the major themes I'd like to see us work on next: While those are grand and nice goals I'd like to see some progress in tiny bits - just verifying some basic deficiencies in packages uploaded on hackage. 1. Would be nice of 'cabal check' (and cabal upload) would warn user about using outdated packages in constraints. Typically users don't even know they use old vulnerable versions of cryptopackages or broken testsuite packages. Which does not make packaging (and using) such stuff simpler. 2. Would be nice for cabal build somehow check that 'ghc --make' can't access files not present in .cabal file. That way amount of packages with missing uploaded tests could be shunken down. Otherwise we have fun situation. github repos have CI hooks, but 'cabal sdist' result is unusable. I guess the simplest would be to copy/symlink part of sorce tree into temp dir and run 'ghc --make' there. 3. Warn about silly depend, like: - base 4 (instead of base = 4) - base = 5 (instead of base 5) - protocol-buffers == 2.0.14 (instead of trying to follow PVP with protocol-buffers == 2.0.*) Thanks! -- Sergei signature.asc Description: PGP signature ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Re: be friendlier to user (was Re: What's next?)
On 2013-09-07 at 09:00:47 +0200, Sergei Trofimovich wrote: [...] 2. Would be nice for cabal build somehow check that 'ghc --make' can't access files not present in .cabal file. That way amount of packages with missing uploaded tests could be shunken down. Otherwise we have fun situation. github repos have CI hooks, but 'cabal sdist' result is unusable. I guess the simplest would be to copy/symlink part of sorce tree into temp dir and run 'ghc --make' there. sounds like https://github.com/haskell/cabal/pull/1455 ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Re: be friendlier to user (was Re: What's next?)
On Sat, Sep 7, 2013 at 1:29 PM, Herbert Valerio Riedel h...@gnu.org wrote: sounds like https://github.com/haskell/cabal/pull/1455 That‘s great if they’re adding a warning for modules, but it'd be even better if it would warn about any missing files not just modules. For example, extra-source-files that are used for tests. That's probably hard to make a warning for without duplicating builds, but perhaps instead of a warning build should actually do sdist build dist/*.tar.gz. Might be slow though. ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Re: How can I get SSH access to www.haskell.org to upload the Cabal user guide?
Hi, On Sat, Sep 7, 2013 at 7:31 AM, Johan Tibell johan.tib...@gmail.com wrote: The sources (.md) files are already on GitHub. Only for the user guide, not for the website itself (e.g. the frontpage of haskell.org/cabal or http://www.haskell.org/cabal/download.html ). -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Keeping the cabal website in the git repo
Hi all, While the sources of some of the documentation is already in git, much of the website (http://www.haskell.org/cabal/) isn't. I suggest we check it in under a website/ directory, next to the Cabal and cabal-install directories. -- Johan ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
