[darcs-devel] building darcsden

Guillaume Hoffmann guillaumh at gmail.com
Sat Oct 7 15:33:02 UTC 2017


Hi Benjamin,

My mistake, *now* the repository is different from mime-string 0.4,
please try it again. I also uploaded mime-string 0.5 on HackageDB.

Guillaume



2017-10-02 6:44 GMT-03:00 Benjamin Franksen <ben.franksen at online.de>:
> Hi Guillaume
>
> I did not realize that your message referred to the problem with
> mime-string. I solved that by adding
>
> import Prelude hiding (most Applicative operators)
>
> in a number of modules. I have not tried yet if that works with ghc
> versions later than 7.10.
>
> BTW, I see no difference between mime-string-0.4 and your version:
>
> franksen at tiber: ~/src/darcsden > cabal unpack mime-string
> Warning: The package list for 'hackage.haskell.org' is 20 days old.
> Run 'cabal update' to get the latest list of available packages.
> Downloading mime-string-0.4...
> Unpacking to mime-string-0.4/
> franksen at tiber: ~/src/darcsden > darcs clone
> https://hub.darcs.net/gh/darcsden
> Copying patches, to get lazy repository hit ctrl-C...
> ^CUsing lazy repository.
> Finished cloning.
> franksen at tiber: ~/src/darcsden > diff -r mime-string mime-string-0.4
> Only in mime-string: _darcs
>
> Cheers
> Ben
>
> On 10/02/2017 09:43 AM, Ben Franksen wrote:
>> Am 02.10.2017 um 02:14 schrieb Guillaume Hoffmann:
>>> Sorry, indeed on my machine I only tried with GHC 8.2 .
>>>
>>> Maybe we should talk with Simon about whether it makes sense to
>>> support GHC 7.10.
>>
>> I don't want to accidentally break builds in darcs, which is why I
>> always use the oldest version of ghc that darcs builds with, in this
>> case ghc-7.10. It would be pretty inconvenient for me if I had to switch
>> to a newer ghc in order to test whether darcsden still builds against my
>> experimental changes in darcs. So I think it makes sense for darcsden to
>> support the same range of ghc versions as darcs does.
>>
>> And it does, actually: ghc-7.10 works just fine with the small change in
>> darcs/Setup.hs (see my other mail in this thread) and that is probably
>> only needed because I build darcsden together with darcs as a cabal
>> project. Note that this is not yet a stable feature of cabal.
>>
>>> Are ther eany dependencies that force us to comply
>>> with this constraint?
>>
>> Not sure what you mean here.
>>
>> Cheers
>> Ben
>>
>>> 2017-10-01 18:53 GMT-03:00 Ben Franksen <ben.franksen at online.de>:
>>>> Am 01.10.2017 um 21:48 schrieb Guillaume Hoffmann:
>>>>> I am still waitinh for Ian Lynagh's authorizatino to add me as an
>>>>> author of the mime-string package on Hackage's, meanwhile the
>>>>> compilable code of mime-string is at:
>>>>>
>>>>> https://hub.darcs.net/gh/mime-string
>>>>
>>>> This does not compile with ghc-7.10.3, I get several errors like this one:
>>>>
>>>> Codec/MIME/String/Internal/ABNF.hs:134:22:
>>>>     Ambiguous occurrence ‘<$>’
>>>>     It could refer to either ‘Codec.MIME.String.Internal.ABNF.<$>’,
>>>>                              defined at
>>>> Codec/MIME/String/Internal/ABNF.hs:137:3
>>>>                           or ‘Prelude.<$>’,
>>>>                              imported from ‘Prelude’ at
>>>> Codec/MIME/String/Internal/ABNF.hs:2:8-38
>>>>                              (and originally defined in ‘Data.Functor’)
>>>>
>>>> _______________________________________________
>>>> darcs-devel mailing list
>>>> darcs-devel at osuosl.org
>>>> https://lists.osuosl.org/mailman/listinfo/darcs-devel
>>> _______________________________________________
>>> darcs-devel mailing list
>>> darcs-devel at osuosl.org
>>> https://lists.osuosl.org/mailman/listinfo/darcs-devel
>>>
>>
>>
>> _______________________________________________
>> darcs-devel mailing list
>> darcs-devel at osuosl.org
>> https://lists.osuosl.org/mailman/listinfo/darcs-devel
>>
>
>
> _______________________________________________
> darcs-devel mailing list
> darcs-devel at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/darcs-devel


More information about the darcs-devel mailing list