hello ,
my idea is follow major LTS Haskell releases with selected packages,
which is released on quarterly base ( next LTS3 is excepted on
August),
Plus replace haskell-platform package with Haskell-platform pattern
which install set of packages with LTS versions..
weekly changes ( minor versions numbers ) in LTS are easily to follow
with our small set of packages.
Nice idea is have to script like gentoo's 'euscan' which scans
versions in obs versus LTS upstream and send notice to maintainer
about new versions ..
Ondřej
2015-04-29 8:59 GMT+02:00 Scott Bahling
On Tue, 2015-04-28 at 20:07 +0200, Peter Trommler wrote:
Hi Jan,
On 23.04.2015, at 17:14, Jan Matejka
wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi
It's unclear to me what exactly does devel:languages:haskell:lts represents and how to create new packages now.
If I get this right, there is stackage.org/lts which is basicly a list of packages that the stackage.org built and tested they all work together, right?
Now my question is what exactly do we need to do to package that? My idea is to just make the packages as we did before - that is probably using cabal-rpm and using hackage.haskell.org as the upstream sources. But, we will use only the versions used in the given LTS release, right? Good question. Stackage provide there own sources don't they? Stackage won't change hackage sources without a good reason. It would probably easiest to use stackage sources then.
If you setup the cabal config to point to the lts release as
https://www.stackage.org/snapshot/lts-2.3/cabal.config?global=true
then 'cabal-rpm srpm' will download the proper version. Would be nice if it just downloaded the tarball an created the spec and not tried to build the srpm.
-Scott -- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org