Going forward with GNOME-based Onyx #4
Replies: 4 comments 3 replies
-
While that probably is the best way, we can't continue maintaining onyx forever, so there should be some way of letting the users of budgie onyx know that the onyx they're using isn't properly maintained anymore. |
Beta Was this translation helpful? Give feedback.
-
It’s just a metapkg so there’s not really any reason it should break but yeah we could add a post install hook to print a warning or something. (Again, once we have something better that’s been deployed, and not before) |
Beta Was this translation helpful? Give feedback.
-
That sounds like a good idea, ofc the main plan is to, y'know, not force-update people's budgie systems to suddenly have GNOME and GDM |
Beta Was this translation helpful? Give feedback.
-
For sure, don’t want to ever reduce functionality if we can help it |
Beta Was this translation helpful? Give feedback.
-
Going forward, with Onyx being a custom GNOME session, rather than a customized Budgie release, how should we handle packaging and whatnot?
I'm of the belief that we should keep shipping the old onyx as
onyx
and ship the new package asonyx-gnome-session
, but I'd love to hear everyone's opinions on this first0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions