Installing udisks2 fixed the issue with the usb drive not mounting. Thanks. No other package needed to be installed. On Tue, Nov 24, 2020, at 14:26, Neal Gompa wrote:
On Tue, Nov 24, 2020 at 5:50 AM Dario Faggioli
wrote: On Tue, 2020-11-24 at 11:13 +0100, Fabian Vogt wrote:
Am Dienstag, 24. November 2020, 10:35:20 CET schrieb Dario Faggioli:
Now, we can put them there, of course, but that would mean quite a bit of duplication. How can we handle that?
Normally I'd copy whatever the non-MicroOS patterns do, for consistency. However, udisks2 is pulled in through Recommends by gvfs resp. libKF5Solid5, which don't have any effect on MicroOS due to "onlyRequires". (This is the reason why I tell users that setting onlyRequires themselves is a bad idea)
Right.
Should we have some kind of `%package desktop` with common stuff, that then both the GNOME and KDE patterns depends on? Or are there better ways of doing that?
While I don't think the overlap is that much, a pattern for deduplication would probably still make sense.
Ok, cool to hear you think that too.
About how big the overlap would be, well, I think it depends on how we see MicroOS Desktop (and I mean in general, for *any* DE, at least *any* DE that we support during install or with a pattern).
I mean, the GNOME pattern has CUPS and some PPD related packages, because I think that an user should be able to print (with at least some common printer models), without having to fiddle with transactional-update. It has samba, as I guess someone though (as, I don't think it was me that added me... but I may be wrong) that an user should also be able to access shares right after install. It has bluez- firmware so at least some common Bluetooth device works immediately (I see you have bluedevil5 in KDE, but I don't think it brings bluez- firmware in).
If these are things that we thing would be useful to all MicroOS Desktop users, no matter which DE they choose, then they're all candidates for being put in the common pattern.
And note that I'm not saying that, if we do the common pattern thing, we should put all those packages there immediately. I'm just thinking out loud about how it could be used / useful.
I think having a desktop-common pattern that is required by all other desktop patterns makes sense. In fact, I'm honestly surprised that we don't already do this for non-MicroOS desktop patterns.
-- 真実はいつも一つ!/ Always, there's only one truth! _______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org