-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish to DNF / COPR instead #1
Comments
My goal is I want just I'm confused why you confused, an I doing anything wrong? Please give advice! |
I'm not planning to submit to Fedora directly, copr too. |
Making your GitHub repository an RPM repo instead of using COPR which is directly made for that (please read https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/ for real) is a bad practice that should be avoided However, RustDesk probably qualify to be in the official DNF repository instead of being in the COPR repository, so you could also request it to be included in the official repository instead |
You could search on RustDesk's discussion People suggests RustDesk to host its own APT/RPM repository, also submitting to Flathub/Snap Store. But they seems not plan to do it (at least now) since they only have three people(according to the commit history), their workload is very high. From the last situation RustDesk submitting to Flathub, I know they don't want to dealing anything except the software project itself. rustdesk/rustdesk#1537 (comment) If they decide to take over in the future, I won't deny them, but current situation is better than nothing. |
You don't need to be an official maintainer of the upstream package to publish it to DNF or COPR. Basically, if what you want is being able to package manage ( What you are currently doing by making your GitHub repository an RPM repository (instead of publishing to DNF, or even just COPR) is an half solution and bad practice And most importantly, publishing to CORP is both better and simpler than the current situation Publishing to DNF requires that you become an official repository maintainer which is more official |
For submitting to COPR:I'm not planning to do it, because they didn't support direct For submitting to Fedora directly:I don't have enough time and ability to this, sorry, and I think it is not a great ideas to submit this software that has very high releace frequency, instead, COPR or official RPM repo is the better ideas. If you suggesting me to asking RustDesk to no matter create a COPR or submitting to Fedora, I don't think it is possible at this moment, they even don't have the Launchpad PPA! Which has way higher marketshare than RPM based distros. They have NOTHING to distribute their software, and no anybody (except @ besdar is submitting to Flathub, and they have Arch AUR) doing this! And what can I do is create a small APT/RPM repository, and use shell scripts to download their official GitHub Releases. I hope you understand something from this story. Edit: I forgot they have AUR. |
I know..I know, I completely understand the difference between Fedora official, COPR, own repo, as well as the difference between Ubuntu official and PPA, but......this is my best efforts, sorry. |
https://docs.fedoraproject.org/en-US/quick-docs/publish-rpm-on-copr/#_packaging_from_source_tarballs |
Thanks but look what I'm found...
|
I also failed to publish it on COPR myself https://copr.fedorainfracloud.org/coprs/malix-off/RustDesk/ Even a manual build from https://github.com/rustdesk/rustdesk/blob/master/res/rpm.spec : https://copr.fedorainfracloud.org/coprs/malix-off/RustDesk/build/8111515/ Here is the log : https://download.copr.fedorainfracloud.org/results/malix-off/RustDesk/srpm-builds/08111515/builder-live.log.gz |
Note that they seems use lots of non standard procedure while building, they existed in |
I just noticed, it will be a PITA to repackage, but i'll try Check https://copr.fedorainfracloud.org/coprs/malix-off/RustDesk/package/rustdesk/ |
failed but succeeded ? |
Deleted my previous comment before having posted the second |
They don't have real tarball, and they're using custom build procedure and didn't put any build script in They need https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rustdesk#n195 |
Maybe someone can port from the Arch AUR's PKGBUILD, but it needs more advanced knowledge.
Yes or no, what RustDesk is doing is compile the binary first, and copy and package them into |
I think it's indeed out of my league I published rustdesk/rustdesk#9576 to raise this issue |
|
B2w, Flatpak also hope you build from source too, but due to the complexity of the Flutter, the reviewer accept to build flatpak package by |
I think they absolutely fucked their build process |
It may be the problems on the Flutter, also it may be the reason why Flathub reviewer suddenly agreed that they don't need to build from the source when they heard "Flutter". |
Having worked with Flutter, it is not fun to work with, indeed. |
What they did is using |
I mean sure but now how to actually do it ? |
They have working GitHub Actions haha. |
Yeah but then the .spec file is not enough so broken by design And about the working GitHub action : https://github.com/rustdesk/rustdesk/blob/master/.github/workflows/flutter-build.yml Absolutely uncanny |
Over 70k stars project and still only 3 people working on this project, this is more uncanny. |
Yeah definitely, you're kind of brave to even attempt to make it to work, and I was very delusional to think I could even try to build from source |
However, maybe rpmfusion could accept it? |
It is built from |
Wouldn't it be possible to build from source though ? |
I just hope RustDesk can have its own APT/RPM repo, Cloudflare R2 may be the great solution. |
The best thing would be COPR technically |
Not possible in short term |
True |
Have you read https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/ ?
Is your goal to publish to DNF or COPR, or to make your own RPM repo from this GitHub repo ?
The text was updated successfully, but these errors were encountered: