[haskell-llvm] Upcoming release, high level binding state

[Nathan Howell]

Last time I checked the builds were failing because LLVM isn't installed on
the build farm.
On May 14, 2013 1:10 PM, "Carter Schonwald" <carter.schonwald at gmail.com>
wrote:

> on a relate note: looks like the current hackage version failed to build
> on hackage, anyone know why?
> both the llvm and llvm base libs
> http://hackage.haskell.org/package/llvm-base-3.2.0.0
> http://hackage.haskell.org/package/llvm
>
> (i'm still learning how the bindings are glued together so i'm not sure
> how to interpret the hackage log)
>
>
> On Tue, May 14, 2013 at 4:03 PM, Henning Thielemann <
> lemming at henning-thielemann.de> wrote:
>
>>
>> On Fri, 26 Apr 2013, Bryan O'Sullivan wrote:
>>
>>        Is there any release procedure beyond the obvious
>>> tag-and-upload-to-hackage I should be aware
>>>       of?
>>>
>>>
>>> Not really. When I was actively maintaining the package, I'd do roughly
>>> the following:
>>>  *  cabal sdist
>>>  *  Build the package and run the tests from the resulting tarball (not
>>> from the git tree), since it's easy
>>>     to miss important files in the tarball
>>>
>>
>> I have put the packages cabal-scripts and darcs-scripts to Hackage that
>> do e.g. this testing from a tarball.
>>
>> http://hackage.haskell.org/**package/cabal-scripts<http://hackage.haskell.org/package/cabal-scripts>
>> http://hackage.haskell.org/**package/darcs-scripts<http://hackage.haskell.org/package/darcs-scripts>
>>
>>   *  Try with all supported versions of LLVM (whatever those are today)
>>>  *  If everything is good, tag, upload, and push
>>>
>>
>>  My convention has been to number the Haskell package based on whatever
>>> current version of LLVM it is
>>> targeted at, so LLVM 3.2 -> llvm-base 3.2.0.0 and so on.
>>>
>>
>> You may use a slightly modified PVP where the first three numbers (not
>> only the first two ones) constitute the major version. This way you can
>> make API changes during one version of LLVM. I also find it an advantage to
>> increase the package version number in the repository right after a Hackage
>> release. This way I can work with versions of the llvm package both from
>> Hackage and from git.
>>
>> ______________________________**_________________
>> Haskell-llvm mailing list
>> Haskell-llvm at projects.haskell.**org <Haskell-llvm at projects.haskell.org>
>> http://projects.haskell.org/**cgi-bin/mailman/listinfo/**haskell-llvm<http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-llvm>
>>
>
>
> _______________________________________________
> Haskell-llvm mailing list
> Haskell-llvm at projects.haskell.org
> http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-llvm
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://projects.haskell.org/pipermail/haskell-llvm/attachments/20130514/ca3b6c84/attachment.htm>