I don't know how much more positive purpose this thread can serve - if you can, please contribute, if you can't, reaching out directly to zypper contributors who can would probably be more productive than pontificating in this mailinglist, especially if you're going to get snippy with someone who was trying to help you
I missed this - you have already answered my own [slightly sniping question from my summary email regarding the place for design].
How does one make a contribution, if the articulation of the problem results in hostility? My initial email was quite clear.
You've not been exactly "friendly" this entire conversation. Each time someone tried to help you or otherwise explain the situation, you've just shunned them saying "I already know that so stop talking about it, the issue is that zypper is broken because --no-allow-vendor-update is too long, etc." I think most people would agree that Tumbleweed has a documentation problem (for many historical and community related reasons). But you're not going to convince anyone to help update the documentation if you're going to be hostile as soon as someone tries to explain the situation.
where i come from we dont go from notion to implimentation, engineering is a process. Linux distros give one a glimpse of the resistence to systemd, a well engineered solution which treatens a cottage industry of confusion.
Speaking of derailing threads, this is one sure-fire way of getting people to start shouting. [I, for one, don't agree that system is a "well engineered solution". Engineered solutions have a scope, systemd (as a project) does not.] -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org