From software to package

Warning

Few steps towards software reproducibility

From source fo applications.

Card done.

tools : cmake, meson, pyproject, docker (as helper in dev process), CI to build, run, test, share with collaborators ...

Anything to step from a set of sourcefiles to something usable (libs, binaries, ...) in a given environment Keywords : automation, documentation Done by developers of the software

Result : a repo, with doc, tools, recipes Somebody can download the repo, apply the recipes and get a binary to execute the process (assuming a proper environment) (a kind of package ...)

Audience : developers of the software

Package builder

(proper terms ?)

From a repo (previous step) to something that can be uploaded and made available somewhere Tools : guix (write recipes), docker (write Dockerfiles from repo to registry), cpack, pyproject, ...

Result : a "package", ready to be put "upstream"

Example : write some Dockerfiles and recipes to made them available in registries or everything to be apple to run "pip install ."

Audience : developers, user, somebody in the middle

Package manager

Point of view : somebody who wants to execute/run a software easily One shot to prepare environment and "install" the software

Example : apt get, docker run, guix install ...

Res : a binary or libs + the proper env to execute it

Pas sur que cette dernière partie soit pertinente du point de vue repro ? Oui si on insiste sur la manière d'utiliser ces outils (fixer une version, un sha ...)