On 04/11/10 17:22, Peter Simons wrote:
> Hi guys,
>> I have released the current state of archlinux and cabal2arch on
> Hackage, but not yet on AUR so that we have the chance to test the new
> release a little.
>> In a couple of days, I'd like to re-generate all our PKGBUILD files with
> the current version of the tool chain to ensure that the files are
> consistent, i.e. that ${_hkgname} is available, etc.
>> IMHO, the next step after that is to set --enable-shared for libraries.
This is a minor point, but is the new version of archlinux (0.3.5)
really API
compatible with the previous version (0.3.4)?
If the answer is 'no', then the never version ought to be 0.4 (or 0.4.0).
(Actually I suspect that I made a mistake already when releasing 0.3.4, it
should probably have been 0.4 to signal the changes in the API back then.)
I would also argue that cabal2arch is bumped to 0.8 (or 0.8.0) to
clearly mark
that the UI has changed and isn't compatible with the previous version
(0.7.5).
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20131012/9611c9ad/attachment.sig>