I would like to build and package a particular Go program. The packaged versions of said program provided by Ubuntu 18.04 and Debian 9.5 (actually PVE 5.2) are all fairly old, compared to what I could get from upstream.
Getting the dependencies for my build right isn't an issue, neither is building a Debian package (been there, done that).
What I need to know is how I can assign a version to my package - which isn't going be released to anyone else - such that should the package maintainer ever release a newer version than my package has, it would get installed and replace my own package (one such situation could be Ubuntu's
Is there some way to "tag" a package in such a way without breaking the internal version comparisons (
I know the backports typically have
bpo in the package name (or is that the version?), but it would be hard to find a comprehensive list of all similar "tags" and so I was thinking perhaps there is already a method to achieve this and avoid clashes. So the main goal is to play by the rules, all the while getting the newest version I can get.