Originally posted by twice
View Post
When we introduce sol to phase out eopkg, it will use different internal databases and automatically record dependencies introduced through a given selection operation, so that when the time comes for the package to be removed, any automatically installed items no longer referenced will be selectable for orphan removal. My stance is that I won't do anything half-arsed, and the implementations I've seen to date definitely justify that label. As with all things in Solus, if we're going to do it, we're going to do it properly.
Comment