[opensuse-haskell] Moving forward: Selecting package versions
Hi, Currently we have in TW Haskell Platform, a set of ~35 packages at exact versions, and pandoc with an ad-hoc selection of package versions. Haskell Platform has not seen an update since summer last year and pandoc cannot be updated without breaking Haskell Platform. For that reason it has been suggested to abandon Haskell Platform. So I would like to start a discussion: How do we select versions for our Haskell packages? How can we coordinate updates, deal with conflicting version requirements? I am looking forward to hearing your opinions. Peter -- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org
Hello,
my proposal is : follow major LTS haskell version eg
http://www.stackage.org/lts/2 , in agust move to
http://www.stackage.org/lts/3 etc.
for now prepare in devel:languages:haskell:lts current major LTS
Haskell, and after we get funcionality on pair with current
devel:languages:haskell switch all
packages to devel:languages:haskell , openSUSE_Tumbleweed
for future:
in devel:languages:haskell:lts next major version of LTS
in devel:languages:haskell current LTS ,( not whole , of course ,
selected set of packages ==> development tools, pandoc , yesod atd.)
prepare latter : "haskell-platform" with similiar set of packages
as haskell platform in past
Ondřej
2015-04-07 11:30 GMT+02:00 Peter Trommler
Hi,
Currently we have in TW Haskell Platform, a set of ~35 packages at exact versions, and pandoc with an ad-hoc selection of package versions. Haskell Platform has not seen an update since summer last year and pandoc cannot be updated without breaking Haskell Platform. For that reason it has been suggested to abandon Haskell Platform.
So I would like to start a discussion: How do we select versions for our Haskell packages? How can we coordinate updates, deal with conflicting version requirements?
I am looking forward to hearing your opinions.
Peter
-- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org
-----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? Here's my first suggestion. To keep things clear I think we should follow project naming of devel:languages:haskell:lts:<lts-major-version>.<lts-minor-version> To make it easier to immediately see what is what and probably have less hassle when switching "what lts version we currently have in opensuse" and "what lts version we are currently preparing to have in opensuse". The proposal was
for now prepare in devel:languages:haskell:lts current major LTS Haskell, and after we get funcionality on pair with current devel:languages:haskell switch all packages to devel:languages:haskell
So there is my second question - how the switch will be implemented? Is it enough to just point the <repository path=...> in devel:languages:haskell metadata to the LTS project? And finally, how will addition of packages that are not present in LTS handled? - -- Jan Matějka | QA Engineer for Maintenance SUSE LINUX s.r.o. | https://www.suse.com/ GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCgAGBQJVOQxSAAoJEIN+7RD5ejahomoIANy851zK3JR4cNqIK7E/pWds WWH76w8Ju01rhauis2l66pW2pg0Iwa1o5Od4dPqa+aXWC5Fn7boHZgh3sKEmTHRN cGv9rW/Np56VBYj897ICUa2sJtBz4XleFozCwYNCfrKtibXgSTA2slKWRWK2hfxa NO6+1orOO+Dfp93MwFXNnUztBFAGyZ2LQkJkXwzPrYSkc9a7WZgwGR1MhPZ4QAiG VzmQaeqnrztKhlHbrDnviONJzJCqNlmKOXslEc2ebQfnwr/pPny5CgrFLvSSla66 JUUuK0uhm/mkz3+qtvsqJmNTXhkX3Fa3geMA0MhZorpY7tUVB1jX11kumnhEDZM= =i8Or -----END PGP SIGNATURE-----
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.
Here's my first suggestion. To keep things clear I think we should follow project naming of devel:languages:haskell:lts:<lts-major-version>.<lts-minor-version> To make it easier to immediately see what is what and probably have less hassle when switching "what lts version we currently have in opensuse" and "what lts version we are currently preparing to have in opensuse".
Good point. Perhaps a note in the description of project d:l:h:lts would be sufficient. We still need to decide, however, which version of LTS we are going to package and how frequently we want to do an update. And we also need to decide what to do with haskell-platform: Drop haskell-platform and all packages that are now leaf packages? Keep Haskell Platform packages but follow LTS versions?
The proposal was
for now prepare in devel:languages:haskell:lts current major LTS Haskell, and after we get funcionality on pair with current devel:languages:haskell switch all packages to devel:languages:haskell
So there is my second question - how the switch will be implemented? Is it enough to just point the <repository path=...> in devel:languages:haskell metadata to the LTS project?
I was thinking of SRs against devel:languages:haskell and then forward to Tumbleweed those packages that are already in TW.
And finally, how will addition of packages that are not present in LTS handled?
I'd say we use whatever we can get to work with the packages we already have :-) Peter-- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org
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
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
On 29.04.2015, at 08:59, Scott Bahling
wrote: 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. Or better yet, create or update an OBS package instead.
/Peter -- Prof. Dr. Peter Trommler email: peter.trommler@th-nuernberg.de Technische Hochschule Nuernberg phone: +49-911-58 80-16 63 Faculty of Computer Science fax: +49-911-58 80-56 66 Postfach 31 03 20, 90121 Nuernberg office: Hohfederstrasse 40, 90489 Nuernberg -- To unsubscribe, e-mail: opensuse-haskell+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-haskell+owner@opensuse.org
participants (4)
-
Jan Matejka
-
Ondřej Súkup
-
Peter Trommler
-
Scott Bahling