Removing files pulled in by packages reliably?
So, the
cosmic-greeter package also pulls in the entire Cosmic desktop, whilst I can't change that, is there a good way to make absolutely sure that the COSMIC Session won't appear on the greeter?
Whilst the lazy way of just blanking out the session's .desktop file worked for sway, that does not seem to apply to the COSMIC session, which still appears in the image, so this is not consistent enough. Removing the other cosmic-* packages isn't possible as that throws an rpm-ostree conflict (duh)
Anyone got ideas?Solution:Jump to solution
i misremembered we added
remove: to the files module, but in any case, this is how easy it should be
```yaml
type: script
snippets:
- rm /path/to/cosmic.desktop...14 Replies
You could try removing the
.desktop file completely instead of blanking it outbeing honest here I'm a bit lazy and assumed that would require a custom module
either that or I've skipped something by accident
Solution
i misremembered we added
remove: to the files module, but in any case, this is how easy it should be
make sure to add that after the package installation in the module list
another thing you could try if you're on F41+ is installing what you want with
dnf5 and trying to find out if it installs the unwanted dependencies or if it can be configured to not install some of thoseoh hey that's neat, thanks for the heads-up! <3
I can use dnf5 since F41 despite being atomic? Is that what you're trying to say here?
Just make sure to specify
dnf5 specifically cause dnf is cli-wrapped by rpm-ostree on Ublue base imagesyes, fedora atomic is slowly migrating from rpm-ostree to bootc & dnf5
and dnf5 can now be used to install packages on atomic F41+
oh thats actually kind of cool, does this require any additional setup or could I do this on a live system?
AFAIK the commands should jusi be available to you on the latest version
try running
bootc statusoh yeah that does work, though
dnf5 hits the RPM Lockfile being on a read-only FS (which makes sense, that is kinda the point)yeah
idk if local layering works yet, but in the image build it should work
we're actually building a module to replace
rpm-ostree with thatthat's actually hella cool, thanks for telling me!
I wonder if dnf5 has any speed advantages over using
rpm-ostreeyes, and dependency resolution too
i hear that installing steam should just work
whereas before it was hellish
hell yeah, I'll be playing around with that on a separate branch :P