Hi all,
I've uploaded release candidates for Cabal-1.18.1.3 (to be shipped with GHC
7.8) and cabal-install-1.18.0.3.
You can install the RCs like so:
cabal install http://johantibell.com/files/Cabal-1.18.1.3-rc.tar.gz
http://johantibell.com/files/cabal-install-1.18.0.3-rc.tar.gz
It's especially
* Henning Thielemann [2014-02-28 22:48:59+0100]
> Am 28.02.2014 22:31, schrieb Roman Cheplyaka:
> >* Henning Thielemann [2014-02-28
> >22:21:39+0100]
> >>>[1]: http://hackage.haskell.org/package/hse-cpp
> >>
> >>It would still be nicer to have a solution that also works with HSC,
> >>CHS and may
Am 28.02.2014 22:31, schrieb Roman Cheplyaka:
* Henning Thielemann [2014-02-28 22:21:39+0100]
[1]: http://hackage.haskell.org/package/hse-cpp
It would still be nicer to have a solution that also works with HSC,
CHS and maybe others. I have also not checked LHS so far.
hse-cpp takes care of
* Henning Thielemann [2014-02-28 22:21:39+0100]
> >[1]: http://hackage.haskell.org/package/hse-cpp
>
> It would still be nicer to have a solution that also works with HSC,
> CHS and maybe others. I have also not checked LHS so far.
hse-cpp takes care of .lhs, too. As for .hsc and .chs, those are
Am 28.02.2014 22:06, schrieb Roman Cheplyaka:
* Johan Tibell [2014-02-28 21:23:23+0100]
* How can I access modules that are preprocessed? HSC processed modules
are stored in dist/build, but CPP processed modules are not stored anywhere.
Perhaps because GHC applies CPP "on the fly". I guess y
* Johan Tibell [2014-02-28 21:23:23+0100]
> > * How can I access modules that are preprocessed? HSC processed modules
> > are stored in dist/build, but CPP processed modules are not stored anywhere.
> >
>
> Perhaps because GHC applies CPP "on the fly". I guess you prefer to use
> haskell-src-exts
On Fri, Feb 28, 2014 at 9:04 PM, Henning Thielemann <
lemm...@henning-thielemann.de> wrote:
> Following Mikhail Glushenkov's advice I have prepared a separate tool that
> checks PVP compliance of imports as proposed in:
> https://github.com/haskell/cabal/issues/1703
I added some feedback in th
Following Mikhail Glushenkov's advice I have prepared a separate tool
that checks PVP compliance of imports as proposed in:
https://github.com/haskell/cabal/issues/1703
There remain some problems:
* How can I exclude automatically generated modules like Path_*.hs from
the check?
* How can
On 2014-02-27 at 20:23:59 +0100, Erik Hesselink wrote:
> On Wed, Feb 26, 2014 at 4:01 PM, Johan Tibell wrote:
>> On Wed, Feb 26, 2014 at 3:51 PM, Tillmann Rendel
>> wrote:
>>>
>>> 1. change `cabal init` to use the pretty printer.
>>> 2. expose the pretty printer at the command line.
>>
>> Agree
+1 on changing the format.
Picking a specific format is bound to annoy some people, but I don't think
anyone prefers the current one. The last option mentioned looks the best to
me.
- Adam
On Thu, Feb 27, 2014 at 8:23 PM, Erik Hesselink wrote:
> On Wed, Feb 26, 2014 at 4:01 PM, Johan Tibell
10 matches
Mail list logo