Perhaps is it just a matter of expectation?
Would it be a no brainer for most Linux people to just reinstall a package that no longer works and expect config files to remain untouched?
I just cannot wrap my head around how it could be such a cost of time to let yay issue a prompt when a major script like python may potentially break scripts.
Sure. Makes sense, yeah. But apparently thatās not how it works. Reinstalling does just thatā¦ reinstalling. Rebuilding is another animal.
why not send a feature request at the source?
Thanks for suggesting. I was thinking along that line
It does sound like a feature yay would be the most direct stakeholder?
the only one aside from the maintainers would start updating PKGBUILDS when dependency changes needs a rebuild.
The package maintainer seems ideal, though it does introduce human latency in the mix.
What would be the drawback of rebuilding each time a script version is updated?
it can fail, or the application you rebuild is not updated to work with the changed dependencyā¦ if we talk about rebuilding automatedā¦ user will not catch issues if he do not manually run the rebuild. There should be a request in the terminal asking for permission j/n on that at least giving a short info to make user understand what it is aboutā¦
I agree on that option.
I hope some day using Linux can be as easy as driving a car.
How could yay be the optimal stakeholder when checkrebuild is a dependency?
Could eos-update terminate by outputting checkrebuild -v with some adequate message?
As prophylaxis I opted to write an update script:
#!/bin/bash
eos-update --yay
echo -e "\n*** option ***\nyay -S package-name --rebuild\nfollowing packages\n"
checkrebuild -v
read
Using Linux is easier than driving a car, remember you are on a rolling distribution if you were on a point of release distribution you wouldnāt have had this problem. Arch is DIY, so why blame this on Linux while this is a rolling release distribution thing? You chose to use EndeavorOS/Arch?
could be eos-update too, i bet @manuel would find a wayā¦
What @Cphusion said is also a truthā¦ Automation leaves an uneducated user in place.
4 posts were split to a new topic: Screwed system after latest python update
I have no idea how the word āhopeā can ever evoke the word āblameā.
The essence of open source is figuring out how to improve features through collaboration.
When a code set has a dependency set, if some script all the sudden fails, is it not the evidence there is an opportunity to manage said dependency set at some point in the tool chain?
Whenever I compile the code I write, I do not feel the need to know which library or which script version runs under the hood, unless something breaks.
Thanks for those who helped.
Logging out.
Sorry English isnāt my first language but what I meant was, you mention you hope that one day using Linux will be as easy as driving a car. From my interpretation of how you phrased it it seemed like you were hinting at that using Linux is harder than driving a car, which it is not.
By hinting that Linux is harder than driving a car I got the impression that you were complaining about Linux not being easy enough because usually not many people complain if something is easy enough.
I may have understood you wrong or it may have come over wrong because the problem with just reading text on forum and even in chat messages is that itās hard to tell the emotion and feeling behind someoneās words. If I understood that part wrong about you hoping that Linux will one day be as easy as driving car, I would be curious to understand what you did mean by that if it was not blaming Linux for not being easy enough?
I close this thread as this is for notification, users will get confusion if we start discussing issues in detail and going deep into suggestions.
Everyone can link to this thread if needed.
But go open a new thread in case of actual issue with the python update or suggestions for the distro.