[DISTRIBUTION] Publication on debian repos/snap store/flathub

[d3v-S]

Hi, I was just wondering whether you have any plans to put this project on debian repo (incase they do not approve) or snap store? I have no issues installing the deb file, but I prefer using repo just for the trust it comes with and maybe there are many like me out there, I guess.

[dawidm]

Hello! It would be obviously great for the application to be published on the official repositories. Unfortunately I don't have any experience with this, and I'm not sure what it takes to be approved for example in the debian repos. I'll have that in mind, try to get to know more, but so I can't promise anything so far.

I wasn't considering snap (that's probably because I use Mint Linux where it's disabled by default), but I put publishing on Flathub on a to-do list some time ago. I will try to make it happen in possibly near future. As far as I understand, flathub wouldn't be any worse that the snap store?

I will keep this request open in case someone is willing to help with any of the option considered.

[bongochong]

I would like to second this, but in regard to RPM-based distributions like Fedora. If you can share the .spec or src.rpm that you use to generate RPM builds, I'd be happy to maintain a regularly updated COPR repository for Cryptonose.

[dawidm]

I would like to second this, but in regard to RPM-based distributions like Fedora. If you can share the .spec or src.rpm that you use to generate RPM builds, I'd be happy to maintain a regularly updated COPR repository for Cryptonose.

Thanks for your interest. Unfortunately I probably can't help with this for now. I don't know much abut RPM packages. I get all the packages: DEB, RPM, windows installer using jpackage tool from JDK - one command on Linux generates both DEB and RPM and as far as i know, it's not possible to generate .spec or .src.rpm using jpackage.

[bongochong]

Well, your RPMs work just fine, so it's not a pressing issue or anything. I'll eventually start playing around with piecing together a spec file, though I'm still kind of new to the packaging world so it might take a bit.

[dawidm]

I did a bit more research and as far as I know, the jpackage tool is generating these files, but removing instantly after creating the RPM. There's an option to not to remove them but it doesn't work for me as expected. But knowing that they are somewhere for some time it's possible that I can provide them, just give me some time ;)

[dawidm]

@bongochong This is a spec file generated by jpackage (I've added txt extension): cryptonose.spec.txt All the files used in spec ale also generated - I modified cryptonose build script to easily create everything with a single command ./gradlew jpackage -PgenerateRpmTmp=true (needed files are put in jpackageRpmTmp folder). Let me know if you still want to try to create the repository. As far as I understand how it should be done, before install phase, cryptonose git repository should be cloned and compiled using JDK (version 15) with mentioned command.

[bongochong]

Thanks so much @dawidm! I'm on a little trip, but will be back in a couple of days. I'll definitely get into modifying that spec for Fedora (and hopefully other distros in the RHEL ecosystem). If all goes well, I'll probably start hosting a COPR for builds of Cryptonose, and eventually propose it for inclusion in the standard repositories.