-
Notifications
You must be signed in to change notification settings - Fork 1
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
Submit budgie-desktop into Fedora proper? #2
Comments
I'm sorry because I didn't respond this issue because the git repo of budgie-desktop has low activities. Is it still acceptable to submit Budgie into Fedora? |
Absolutely. It's still maintained by @ikeydoherty, so there's no reason not to. |
+1 on this |
It has low activity because Budgie 10.x is basically LTS and will only see brief periods of activity, but mostly just minor fixes (no real new features) |
This would be really helpful. |
With the current development of Budgie, I think I will stay with copr. |
What about the current development of Budgie means that you will stay in copr only? |
@Conan-Kudo Yes. Sorry about this, but the Mutter issue has given me some worries because I am not familiar with Vala (not interested). I see pantheon desktop also suffered because of that issue[1], finally there are two packages of mutter in repository. Also, it's already a year after the latest release (Budgie 10.4) and it fails to build on Fedora 29+. [1] https://decathorpe.com/2018/09/04/call-for-help-pantheon-on-fedora-29.html |
There are already pull requests for porting to GNOME 3.30 platform: https://github.com/solus-project/budgie-desktop/pulls |
@Conan-Kudo But, you can't apply those patches to Budgie 10.4 tarball, it fails. So many changes happened. Any advice? |
I could probably help create backport patches for this. Let me make some time for that. |
Thank you @Conan-Kudo. I will give my best too. |
Is there a reason you haven't submitted Budgie into Fedora itself? The last package review for budgie stalled out a while back, so a new package review would be welcomed!
The text was updated successfully, but these errors were encountered: