Use Travis CI to create and publish packages to GitHub and/or upstream/private repositories

[jmealo]

Have you considered creating packages using Travis as part of the build process?

I tried to do some of the legwork/research and document it in this ticket. It might be worth just firing off an email to each distributions mailing list to see if someone is willing to sponsor sqitch or even create/maintain the sqitch package for you.

Where to submit packages for inclusion in upstream package managers:

• Debian/Ubuntu
• SmartOS/NetBSD/Minix
• Arch Linux
• Fedora
• Redhat/Fedora (unofficial)
• Gentoo see note on not submitting CPAN builds

Where to host packages unofficially:

• Ubuntu: I've seen a fair number of PPAs hosted on launchpad.
• SmartOS/NetBSD/Minix (they recommend niche packages be hosted on GitHub, so if you cannot find a sponsor, GitHub releases are an option)

Relevant links:

• GitHub Releases Uploading
• Effing package management! Build packages for multiple platforms (deb, rpm, etc) with great ease and sanity.
• How to package for Debian
• Ubuntu packaging guide

I haven't used FPM personally, but its goals are noble and it claims to do something that should speed things up:
The FPM documentation doesn't say that it supports CPAN as a source, however, if you view the tests and issues there appears to be support in some form or another.

If you don't want to tie the Travis CI and release uploads to however you manage Git, it'd still be pretty easy just to push the packages into S3 or something comparable without using the official workflow.

[theory]

In this vein, there is now a Docker image. See the docker-sqitch project for the implementation.

[jmealo]

@theory I can't tell if we should be happy or sad that it's easier to make a docker container than an OS package. Thank you for the update.

[theory]

I don't know if it was any easier, but I was motivated. 🤷‍♂️