Open datgausaigon opened 2 months ago
We will gladly cooperate and help hosting such repos but we do not have in-house expertise in this domain.
Hi, @romange Thank you very much for your reply ❤️. We will discuss this issue with engineers. If we can help, please accept this help.
Hi, @romange I have found an immediate solution, which is to ask for help from EPEL. Let's try contacting fedoraproject.org and ask them for help creating a repo for Dragonfly on EPEL.
https://docs.fedoraproject.org/en-US/epel/ https://docs.fedoraproject.org/en-US/epel/epel-package-request/
it's not gonna work because Dragonfly license is not OSI compliant. We must maintain our own repos.
hmm, I actually see that they actually attempt to integrate dragonflydb. https://repology.org/project/dragonflydb/packages
I am not sure what's the status of this effort. Can you please DM me on discord? We can sync there on how to proceed with this.
This is the package build file: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dragonflydb
This is the package build file: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dragonflydb
@romange Yup, this is the package build for Arch Linux.
https://repology.org is the packaging hub
Repology monitors a huge number of [package](https://en.wikipedia.org/wiki/Package_(package_management_system)) [repositories](https://en.wikipedia.org/wiki/Software_repository) and other [sources](https://repology.org/#repos-footnote) comparing packages versions across them and gathering other information. Repology shows you in which repositories a given project is packaged, which version is the latest and which needs updating, who maintains the package, and other related information. Repology might be useful
Yes, I've read a bit about ArchLinux - they allow non-OSI packages but this won't be the case for fedora/debian distributions, so I am afraid it won't be possible to add DragonflyDB to standard repos.
This issue is being clarified and gradually resolved. Can you tell me more about non-OSI packages. The links talk about "non-OSI packages".
Oh, I found out that your license is BSL 1.1 (Business Source License) - Not the source code license. And according to the copyright documents you publish after September 1, 2028, you will change the license to Apache License, Version 2.0. Am I understanding this correctly? And if that's the case, then not all Repo Hosting supports storing "non-OSI packages". ArchLinux is a "Hacking OS" and they allow non-OSI packages. And finally, the best way is to host the Repo for Dragonfly yourself.
Yes, it's all true. And that's what I asked to help with - we can host the repo but we would appreciate the help with all the code around building such repo and pushing it to a static storage. Basically, we've never done such a thing (hosting a custom repo) and would like some help from someone who has experience with that.
Hi, We are integrating Dragonfly into our open source software that has many users. We are facing a problem: Dragonfly currently does not have Repositories to support installation. This makes it difficult for current development as well as updating our software with your Dragonfly in the future. Can you build Dragonfly Repositories specifically to support Linux distributions?
Thanks ❤️