Removing dependencies that are not needed.

DataDrake

Cossty There isn't going to be a fix. eopkg is in maintenance mode and we'd rather not break it further. If someone manages to track down the cause, I'm amenable to a PR for it, but Josh and I have much bigger fish to fry.

Cossty

DataDrake I'm not going to pretend that I know more than you, but wouldn't it unnecessarily bloat Solus after a couple of months/years if dependencies are not removed correctly? You probably have more important things to worry about, as you said, and this currently isn't that big of an issue. I'm just curious.

Girtablulu

DataDrake Could it be a "chain dependency" issue? like breeze pulls in needed deps to run and these deps pull in some other etc etc, does eopkg handle such cases nicely?

Cossty

Staudey I uninstalled almost every application that came with Solus and some unneeded dependencies too. It might have been one of those. Lutris installed glibc 32bit. I don't think that package is necessary for Solus to run. After your message, I checked glibc 64bit and software center didn't let me remove it. I might be wrong, though. You probably know more about Linux than me.
I'm pretty sure that system was updated before I started removing and installing packages.

DataDrake

Cossty Bloat is relative I suppose. Generally, this feature seems to work, so I don't believe its wholly detrimental for it to go unfixed. For me personally, I'd hope that we might be able to retire eopkg long before that becomes an issue.

brent

if it's not a bug the only card to play is sudo eopkg check. Something doesn't smell right about any of this. You canit packages but there is no way to rm them. If it's not a bug and I was a betting man , something is broken. At the very least you would remove all doubt (edit): that you did all you can on your end.

Can't answer for datadrake, but a couple excess packages to many aren't "unnecessary bloat" but personally I would draw the line at 5 or more. Lot's of schools of thought about bloat that is for sure.

Cossty

DataDrake oh so you want to replace whole package manager for something else? I didn't know that. Mind sharing something more? Like, will it be something new or fork of existing one? Or is there somewhere post where I can read something about it?

DataDrake

Cossty I don't know that I have a specific post somewhere to link (someone else here probably remembers better than I do), but we announced years ago that we'd be replacing eopkg. I've been replicating existing functionality piece by piece inside of libeopkg as I work on it for other simultaneous tooling projects (ypkg 3, ferryd, yabi, etc). Eventually this will be used as a backend library for sol which will be a brand-new package manager. A lot of the technical details I've been keeping close to my chest, but sol will initially be a drop-in replacement for eopkg and will get upgraded later on for new package and metadata formats that I've been developing behind the scenes.

brent

DataDrake I don't know that I have a specific post somewhere to link (someone else here probably remembers better than I do),

[I remember a couple where you talked about the upcoming sol.
https://discuss.getsol.us/d/4719-state-of-development-on-eopkg-sol/4
https://discuss.getsol.us/d/4872-upcoming-hackfest-let-s-go-stateful-configuration-sun-june-14th-at-1400-utc/24]

Cossty

DataDrake thx
I guess you can mark this thread as solved.

Cossty

brent that was very informative. thx

Cossty

Girtablulu You know what, that sounds plausible. I would like to confirm this. Do you know of any application that has “simple” dependencies?

DataDrake

Girtablulu I think it's far more likely that something got accidentally marked as manually installed than anything dep related.

Girtablulu

DataDrake gave it a quick test inside a vm, and yea eopkg removes everything with rmo, so either something else needs it or there was a manual install

Cossty

ok thx everybody

« Previous Page