We have various individual tools to automate parts of the Haskell packaging process, like cabal-rpm, but those tools aren't integrated into a fully automated system that keeps Haskell packages up-to-date with as little human intervention as possible. I would like to build that system. Stackage provides us with an accurate list of packages and versions that are known to work together well, and there are basically two flavors: the nightly snapshot (bleeding edge) and the LTS release (stable API). The former is appropriate for Tumbleweed, IMHO, and the latter is appropriate for stable releases like SLE or Leap.

Now, we can use cabal-rpm to generate spec files automatically for all packages in a Stackage release and check them into OBS. The process does need some tweaking, however, because cabal-rpm generates spec files that don't always work well for SUSE. We could (a) branch cabal-rpm and add SUSE-specific know-how to remedy that issue or we could (b) maintain a set of patches that adapt the generated spec files to our needs. Once the Stackage releases are available in an OBS development project, we need another automated process that submits all updated packages to openSUSE:Factory, etc.

Getting that entire system up and running within a week is probably a bit ambitious, but it should be quite possible to achieve a working prototype that solves 70-90% of the tasks we do manually these days.

Looking for mad skills in:

haskell ci obs bash

This project is part of:

Hack Week 14

Activity

  • over 3 years ago: evshmarnev liked Automate Haskell Packaging
  • over 3 years ago: pluskalm liked Automate Haskell Packaging
  • over 3 years ago: osukup liked Automate Haskell Packaging
  • over 3 years ago: osukup joined Automate Haskell Packaging
  • over 3 years ago: psimons started Automate Haskell Packaging
  • Show History

    Comments

    • osukup
      over 3 years ago by osukup | Reply

      @psimons prepared new way to automate creating haskell packages for rpm based distributions

      results are in opensuse-haskell github repository

      we moved to statically linked haskell applications

      and began with preparing OBS repositories for automated submitting haskell packages

      now wee need prepare config and patch files for differences between generated spec files and suse/distribution specific changes

    • psimons
      over 3 years ago by psimons | Reply

      The automated generation of OBS projects from a Hackage/Stackage config file works nicely. We have added a few thousand Haskell packages to OBS in https://build.opensuse.org/project/show/develadd-emojihaskelladd-emoji6 (LTS Haskell 6.x) and https://build.opensuse.org/project/show/develadd-emojihaskelladd-emojinext (Stackage Nightly). There is more effort necessary to clean up the build process and to create manual patches to remedy issues in the auto-generated spec files, but all things considered we were are quite happy with the results accomplished during Hackweek.

    Similar Projects

    Write a simple ESMTP Mail Transport Agent in Haskell by psimons

    Theoretically, Haskell should be perfect for im...


    obsci - a CI for open build service packages by tbechtold

    Currently it's pretty difficult to create tests...


    Distribution source code repository/browser by mkoutny

    Motivation: You know a particular function ...


    Ruby Gem: Open Build Service API by mschnitzer

    I just recently started a new project which is ...


    Ant Ivy OBS resolver by cbosdonnat

    SUSE Manager uses an ivy repository on the R&D ...


    Migrate more OBS service scripts to pure systemd by enavarro_suse

    Following the work started in the last hackweek...


    obsci - a CI for open build service packages by tbechtold

    Currently it's pretty difficult to create tests...