[Dune-devel] Dune packaging

[Robert Klöfkorn]

Hi Simon,

I think this a good point for the next developer meeting (some time in
the future).

> - easybuild (myself, https://gitlab.math.tu-dresden.de/spraetor/dune-
> easybuild, version 2.6)

easybuild also exists for version 2.8 or 2.9 and both are based on the
pypi packages. It's strange to update these, that's why the effort did
not continue (from my side).

> My point is: we cannot restrict ourself to just one package manager,
> since they all have different scopes (linux distributions, HPC vs
> desktop, python vs c++,...), but currently everyone who works on a
> package management essentially does invent the wheel again. Can we
> combine the efforts?

I think this is a good idea. I'm not sure to what extend it makes sense
to include the pypi recipes into a gitlab repo.
>
> My suggestion is:
> - A central gitlab group for package management recipes, e.g.,
> gitlab.dune-project.org/packaging/ or gitlab.dune-project.org/pkg/
> - People involved in these recipes could discuss some common patterns,
> e.g.,
>    * package naming,
>    * package versioning,

As I have suggested some time ago, a version number including some form
of the year the package was created, which is much more convenient than
the current approach of 2.x.x, where nobody even knows why it's 2 and
not 3 now.

>    * separation into individual modules or a meta-module with variants,
>    * how to include python bindings into c++ packages
> - It would be nice to have easily accessible update-scripts
> - Maybe we even find a way to create/update all different recipes at once
> - In the future, we might want to think about the CPS (Common package
> specification)

This might be a bit more complicated since at least for the pypi packing
process this has evolved while the dune process sort of has not.

> - packaging should be integrated into the release pipeline
> - packaging could be part of the system tests

This is done at least for the pypi packing which is done on github due
to the restrictions with access for the gitlab CI.

Automating at least packages like easybuild and spack should be possible
based on the pypi packages. I'm not sure how this is with the debian
packages, which I actually never have used in the more than 20 years
DUNE exists.

Regards,

Robert



När du skickar e-post till Lunds universitet behandlar vi dina personuppgifter i enlighet med gällande lagstiftning. Mer om hur dina personuppgifter behandlas hittar du på Lunds universitets webbplats<http://www.lu.se/integritet>.


When you send emails to Lund University, we process your personal data in accordance with existing legislation. To find out more about the processing of your personal data, visit the Lund University website<https://www.lunduniversity.lu.se/about/contact-us/processing-of-personal-data-at-lund-university>.

XLU-DISCLAIMER-APPLIEDX