PROCESS IN ORDER TO HAVE CIAO PACKAGES IN MAJOR DISTRIBUTIONS OFFICIAL REPOS
Debian:
Provide the source package along with the debian files in order to request an inclusion to official repositories.(DONE, requires revision/feedback from Debian folks)
Request sponsorship to some Debian developer or someone in the mailing list to include the package.(WIP, would take some time)
Make tests in the Debian infrastructure(first, learn how to use it).
Fedora:
\ The same workflow as Debian.
Request packaging for CIAO missing dependencies(docker) or suggest that we package those.
PROS:
Official distro repositories are naturally trusted.
We don't worry about the packaging process.
CONS:
It could be a long process
As they don't accept packages built from vendored sources. It implies to have to match
the vendor packages versions we are currently using vs the ones in official repositories,
which can be outdated and there is a chance to break the builds
PROCESS IN ORDER TO PROVIDE OUR OWN PACKAGES IN EXTERNAL REPOSITORIES
DEB Packages
PPA repo(DONE via reprepro)
Request hosting
Automate building+testing
RPM Packages
Create a yum/dnf repo
Request hosting
Automate building+testing
PROS:
We could have a better control of the packages we provide(The ones that actually works)
We have people with expertise in packaging and automating the process of building
CONS:
Requires hosting
Package sources may not be trusted as provided by distribution
Based on some discussion today I'm marking this as a candidate for the Sprint 3. We'd love to have this now, but want to focus on the ansible deployment first.
PROCESS IN ORDER TO HAVE CIAO PACKAGES IN MAJOR DISTRIBUTIONS OFFICIAL REPOS
Debian:
Fedora:
\ The same workflow as Debian.
PROS:
PROCESS IN ORDER TO PROVIDE OUR OWN PACKAGES IN EXTERNAL REPOSITORIES
DEB Packages
RPM Packages
PROS:
CONS: