caprine
caprine copied to clipboard
Add packages to official repositories
I see you have already prepared rpm
and deb
packages.
It would greatly improve availability for potential users if you would add them to official repositories.
Currently, users wanting to have automated updates have to use snap, or AppImage (together with appimagelauncher).
Hi!
We actually don't build rpms but we will consider it, however adding to the official repositories is a bit more problematic on Fedora and CentOS since they have a very strict guidelines which we may or may not satisfy and currently don't have resources to investigate and handle.
I'm working on making a COPR repo which can easily be added with one command sudo dnf copr enable username/repo
. I will post the information about it here once I set it up. Keep in mind that the repo I'll make won't contain the "official" Caprine build since I'm building it and not the automated builder. It won't contain any modifications but it won't be promoted as the official build.
Regarding the deb package, I'll see what are the requirements for adding the package to official repos and what's the process for that.
Any help with this will be very welcome and if you have some docs or information that could help, please do share 😁.
Some useful links:
https://www.debian.org/devel/wnpp/
https://askubuntu.com/questions/13255/how-do-i-propose-my-project-to-be-part-of-debian-too
As far as I know Debian packages also require passing some tests.The tool used for them is lintian
.
Even if you find adding these packages for Debian too problematic you can just add caprine to the list of requested packages and wait until there will be someone willing to add it.
What I did is wrote a script to build my own repository server, put all the GIT links in there to be scraped, along with any other debs I wanted included ones that needed to be built. Then I just add the repo server to my sources.list.d and all my applications stay updated through my own repo server!
@sgtcoder that's exactly what I did in my repo [1]. Someone might find this useful so I'm putting the link here. You could link detailed instructions if you have some. I made a shell script [2] for building a deb and rpm repo and signing packages.
That however is not the solution to this issue. The issue is adding packages to official repos, not making a personal one. I've been working on the rpm package [3] and when I find some free time I'll see how to submit it to Fedora repo and pass all the tests. On the Debian side of things, I haven't yet had time to research how the packages are exactly being built (which build system is being used, is Caprine even going to be allowed in the repos...) so that's on hold.
As always, any contributions regarding this issue are very welcome!
[1] https://gitlab.com/dusansimic/repos [2] https://gitlab.com/dusansimic/tinyrepo [3] https://github.com/dusansimic/rpms/tree/main/caprine