On 15.02.2018 19:42, Richard Brown wrote:
All of this would be avoided if everyone was just using spec_cleaner automatically, as that is already able of taking care of the problem I'm addressing.
* format_spec_file reformats my spec file even for local build in ways I don't like * it is probably written in a language I refuse to use and thus I am not able / willing to fix that. * other forced _service runs make it impossible to test build locally without first adding / removing stuff ("foo bar is not mentioned" type errors) * format_spec_file inserts SUSE copyrights for current year for packages, no SUSE employee has touched in a copyright-significant way in almoast decades. And as long as this is the current state of affairs (I only saw the "SUSE Copyright" and the "forced service prevents local build", I'll keep "alias osc='osc --noservice'" in my global exports.
So, ironically we're currently living a situation where your avoidance of spec_cleaner has created both more work for all of us, and more checks for all of us.> I like my job, so I don't think it's worthy of long flamewars^Whealthy discussions, but maybe it's worth thinking over whether your behaviour actually helps with what you're aiming for?
I'm aiming for "maintaining my packages without constant annoyance by tools / policies". I do, for example, deliberately not contribute to projects which have a high paperwork-to-efficiency ratio. FSF owned software for example: last time I looked you needed to sign lots of paperwork with copyright assignment etc. I just don't to this to just contribute a quick fix (for FSF stuff, the work around is usually to just yell "I release this patch into the public domain" and then someone will take it). Or openStack to name a prime example of a project actively trying to scare contributors away with crazy contributor agreements. I like to contribute to the linux kernel for example, where the technical hurdles (the quality bar) is high, but the administrative overhead is low: [x] checkpatch.pl ok [x] signed-off-by added [x] maintainer agrees this is a fix => the patch is in. And if you are a newbie trying to just add the USB ID of your WIFI stick to a driver and are not used to the techy staff at lmkl, there are guys around to help you get your simple patch in (me, sometimes ;-) Until now, openSUSE was below my annoyance threshold, even though rpmlint checks like "FSF ADRESS WRONG IN SOURCE FILE" (something a package maintainer usually has absolutely no way of changing) are trying to push this over the edge. Back to topic: IMHO the only way forward is keeping old SPDX format, at least until the last distributions that have a check for these are out of support (SLES11 currently until 2022-03-31) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org