hyphens As an opening remark, I want you to understand that the following is my honest opinion mixed with actual facts from one of the lead developers of this project. This response is intended to educate and in no way demonstrates animosity toward you or your ideologies.
You are going to be hard-pressed to fine a rolling-release distro that meets all of the requirements for are asking for.
The way that we do packaging on Solus is actually completely incompatible with your intentions. All packages have a monotonically increasing release number. It doesn't get reset every version change and it never goes backwards. This makes dependency resolution trivial and ensures that we have a traceable history of what releases of other packages a given package was built and tested against. eopkg is transactional and atomic, but it is limited to rolling back an entire transaction, and never an intermediate transaction on its own or a part of transaction. Whether you like it or not, that is how we are able to achieve a stable upgrade and downgrade path in Solus.
hyphens should exercise caution playing with that rolling system's continuity,
We strongly encourage you to update every week, never to be cautious about an update.
hyphens reporting issues should only be done when everything is up to date
We only require this because (1) It guarantees that your issue isn't the result of an incomplete upgrade and (2) it puts your system into a known state that we can easily test against.
hyphens if you feel so liable about system breakages when you're offering such unbreakable defaults then might as well remove terminal from the iso and remove terminal programs from the repo and make it impossible for users to escalate privileges. ....... Maybe that's your ultimate goal? to be another ChromeOS or MacOS?
The whole point of a stateless system is for you to easily override default configuration settings and this is something we work towards with all packages. The whole point of sane defaults is not to force you to use our configuration, but to ship a configuration you don't feel the need to change because it "just works" for most use cases.
Our goal has never been imitation. We take great pride in not being like other OS.
hyphens when something has the potential to do some damage toolmakers don't disable it. instead they offer tongue-in-cheek flags like that one or issue warnings with [y/N] prompts.. some require you to write literal words like yes or trust or write.. some package managers require you to specify a version number instead of doing a rollback.. etc..
you shouldn't feel liable after something like that honestly..
This isn't about liability or even prohibiting eopkg to do something we don't think it should. eopkg's fundamental design is incompatible with what you are trying to achieve. I can't give you a flag to use for something it cannot and will not ever do.
hyphens I find this a reoccurring theme in Solus development.. not only an updates matter.
"Solus is a selfish, pragmatic obsession with building a technically excellent linux distribution." If you don't agree with how we do things, you are going to continue to be disappointed and frustrated. Maybe you should start to entertain the notion that your ideologies and desires are fundamentally incompatible with Solus and that you should start shopping for an OS that aligns with your own.
hyphens installer doesn't create an easily editable install-script file, and instead does subprocess calls and native python operations. someone might just edit that shell script and bork the installation after all instead of having to rewrite sections of unnecessarily oo python code. because there are no cases except those that maintainers thought of prior.
The installer will be getting a full rewrite and does not represent what Josh and I think is an optimal solution. And if you hate OO Python code, you are really going to hate us because it will be written in C with GObject. We may consider scripting in the future, but that is not something we think is a necessity for a home computing environment.
hyphens everyone but a select group of maintainers is disallowed to access the iso building scripts, effectively making both the isos and the scripts nonfree software. because software freedom isn't important when some users might produce a badly working iso. because writing a disclaimer that the only approved Solus iso is the one distributed in the getsol.us website is out of question.
Our decision to restrict access to the ISO building scripts has nothing to do with restricting your freedom. It was a difficult decision following the abuse of our tooling by certain individuals to deliver custom ISOs that were shipped with our branding and and that were misinterpreted as coming directly from us. This is both a security nightmare and misuse of our brand. Disclaimers are insufficient to deal with these situations. As they say, one bad apple spoils the bunch.
hyphens i find it inconvenient that i have no option but to sit like a kid on santa's lap and ask for everything from the maintainers..
Then either the way you are trying to effect change isn't in line with normal contributions or the changes you are trying to make aren't ones we are interested in.
hyphens overworking them and causing headaches..
Surely, we are the ones to make that determination, not you?
hyphens especially when y'all are doing it for free without donations even..
This isn't a limitation due to funding. Our ideologies don't suddenly become more flexible in the presence of a surplus of money.
hyphens you could be instead utilising one of the most powerful aspects of a free software community; the community's ability to do the work.
We do. Daily. From dozens of people who contribute patches, translations, code, bug reports, and provide troubleshooting support to the community. You making statements like that is an insult to all of the great work they do.
hyphens give me a robust tool and let me do it my way. then i'd show you what i've done upstream. merge if you like, turn down if you don't, in both cases we both win.
You have that backwards. We are the upstream, not you.
As a closing remark, I want you to understand that I'm not going to keep having these back-and-forth debates with you. I will happily try to better explain our reasoning behind specific decisions if you want. But I have no interest in having ideological debates over what Solus is or should be.
