AlphaElwedritsch So I do that for the update list in the updates section as much as anything, similar to Solus SC. I have changed that to no longer impact the start-up as it works in the background to check now. That removes that from the equation.
Regarding EOPKG issues you are experiencing
Also in looking at the overall impacts I have changed some things on the eopkg side to check the latest history change before refreshing the cache. If the latest change date in history is not newer than the eopkg package cache I create, there is no reason to recreate it. What this will do is, the first launch it will create the cache which will have an impact; however, subsequent launches it will not.
There are caveats to that...
If you use eopkg to install, remove, or update outside Solseek it will need to regenerate the package cache as that will impact the history and make the history date newer than the local cache.
If you install, remove, or update within Solseek or by using solseek it/install, solseek up/upgrade, or solseek rm/remove it will auto regen during the process and will not need to rebuild next launch.
Now as far as it not being able to find your eopkg-index.xml
Could you give me the output of
ls -li /var/lib/eopkg/index/Solus
Just want to see if the eopkg-index.xml is there (not the eopkg-index.xml.xz)
I have not been able to recreate this. I have made some changes to make it more robust, but this one is strange.
I can get why the eopkg -la command could potentially take some time depending on bandwidth and system, but this file should exist unless I am missing something.
In any case, I do apologize that you are having issues and I wish I could figure out why you are having them. It has forced me to research a lot more, and that is good, to make certain areas more robust, but I hate that it is at the expense of you having these issues.
