camper/debian/camper-sqitch.install

6 lines
165 B
Plaintext
Raw Permalink Normal View History

Add Debian package Although it is way too soon to install the application on any server, i use build.opensuse.org as a kind of CI/CD server: it runs the migration and executes the test suite on each commit. For that, i need to build *some* package, and Debian suits be better because it has all the Go packages i use; i would have to create the RPM for many libraries if i were to use openSUSE, for instance. According to the de facto project layout for Go[0], these files should go into a `build/package` folder, but since i already broke the rules with Sqitch’s folders, i do not see why i have to go against Debian’s conventions of placing them into a `debian` subfolder of the root. I have spit the package into the binary and the Sqitch migration files because it is possible to want the PostgreSQL into a separate server, and there is little point of having Sqitch and all its dependencies installed on the front-end server where the Go program runs. The demo package is probably harder to justify, as it is just a single file, however i will not run out of packages, will i? Lintian detects htmx@1.9.3.min.js as a “source-less” file, which is practically true as nobody is ever going to edit a minified source. I did not want to include the source in the distribution package, that’s why i included it in the “missing sources” file, even thought this is a native debian package and, thus, can not have missing sources. git-buildpackage creates a lot of extra files that have to be removed to build it again, otherwise the process detects the new files in the directory and refuses to build the tarball. I was getting tired of doing it manually and added a Makefile rule. Closes #20
2023-07-27 17:20:29 +00:00
deploy usr/share/camper/sqitch
revert usr/share/camper/sqitch
verify usr/share/camper/sqitch
sqitch.conf usr/share/camper/sqitch
sqitch.plan usr/share/camper/sqitch