From: Tom Wijsman <TomWij@gentoo.org>
To: slong@rathaus.eclipse.co.uk
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: dropping redundant stable keywords
Date: Wed, 5 Feb 2014 01:08:33 +0100 [thread overview]
Message-ID: <20140205010833.1bcf8dca@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20140204210319.GA1935@rathaus.eclipse.co.uk>
On Tue, 4 Feb 2014 21:03:20 +0000
"Steven J. Long" <slong@rathaus.eclipse.co.uk> wrote:
> Tom Wijsman wrote:
>
> > They are less work; since it lets the slower arches move their work
> > to bugs of important packages that need their attention, instead of
> > bugs of non-important packages were the stabilization isn't really
> > necessary.
>
> Huh? The slower arch is not keeping up with stabilisation. How can the
> stabilisation suddenly be unnecessary? If it is not needed, there is
> no problem, and we wouldn't be having this discussion.
It is still necessary, as clear from the difference in importance.
> Much better for the arch in question to field the bug, than tell the
> user there is no problem, and we don't care. That way you can get the
> user involved in stabilisation and AT via that bug, instead of turning
> them away with priggishness.
Problems should be visible instead of hidden, as well as resolved. A
move in work means a move in work, further implications are yours...
> > > The arguments and headaches at the user, bug
> > > and AT sides are causing more work (or detracting from real work)
> > > too.
> >
> > Yes, the less work that we can do, the more work the user has to do
> > as a natural consequence; discussions like these are there to
> > prevent those headaches way in advance, as we can proper adapt
> > and/or respond to the situation. And if needed, bring out news such
> > that the user is well informed. Not sure which argumentation this
> > is about though.
>
> Perfectly simple: instead of having this row repeatedly, or borking
> archs, let's use the solution proposed by the ARM AT: provide a
> technical reason why it won't work, rather than a conceptual problem
> with the "hack".
Searching for such technical reasoning is a leeway for hacking & hoping.
Solutions were provided, a policy has been made; we are exactly
avoiding to row repeatedly, and this is yet another solution I propose:
Provide a technical reason why it will work?
You further demonstrate this solution that I propose we should use:
> The history of computing is littered with hacks that turned out to
> shed new light on a problem: it's called exploring the problem
> domain. It's only when you have idiomatic knowledge of the
> language/tools *and* the specific domain, that you can envision
> oddball solutions and more importantly _know_ that they will work
> (perhaps with a bit of tweaking.)
It is called prototyping.
> <snip>
> > [1] Quality Assurance / Policies / Dropping Stable KEYWORDs
> > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies#Dropping_Stable_KEYWORDs
>
> That's not a policy: it's a two-line statement of intent.
It is policy, as it permits implementation of that intent; at the very
least, it is a policy change that allows you something you were disallowed.
> Further, the solution steev brought up is much much better than
> simply dropping the ebuild.
>
> > > Just keep the old ebuilds as useful metadata, subject to the usual
> > > version-control cycle, but iff it's causing you problems and you
> > > want to drop it, mark it with: "-* slowe rarch" so we can script
> > > off it and automate bug-handling etc. so your life is easier, as
> > > well as the archs in question (and their users.)
> >
> > As stated before, -* means something way different; it is a
> > suggestion that does not fit this thread. Like before, did you mean
> > "slower arch"?
>
> No, it's an example, like foo bar, but indicating that we're talking
> about slower archs, and likely more than one in some instances. As
> before did you mean to raise a technical objection with clear
> explanation of what and why it would break?
>
> > And even if you did, we have then already been using this practice
> > for a long while; it is different from the problem that was brought
> > up here.
>
> Yes, yes, you can keep going on about the "conceptual difficulty", but
> the simple fact is the solution works, or it wouldn't have been
> raised. steev's idiomatic knowledge and solution wins, IMNSHO.
"The -* keyword is special. It is used to indicate package versions
which are not worth trying to test on unlisted archs." [1]
You can keep rehashing about "winning", but all it does is break policy.
[1]: http://devmanual.gentoo.org/keywording
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
next prev parent reply other threads:[~2014-02-05 0:10 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 16:33 [gentoo-dev] dropping redundant stable keywords "Paweł Hajdan, Jr."
2014-01-28 16:38 ` Alex Xu
2014-01-28 16:54 ` Tom Wijsman
2014-01-28 17:23 ` Jeroen Roovers
2014-01-28 19:21 ` Rich Freeman
2014-02-03 6:25 ` [gentoo-dev] " Steven J. Long
2014-02-03 9:43 ` Tom Wijsman
2014-02-04 21:03 ` [gentoo-dev] " Steven J. Long
2014-02-05 0:08 ` Tom Wijsman [this message]
2014-02-05 0:23 ` Steev Klimaszewski
2014-02-05 1:07 ` Tom Wijsman
2014-02-05 1:35 ` Steev Klimaszewski
2014-02-05 1:48 ` Tom Wijsman
2014-02-05 3:15 ` Steev Klimaszewski
2014-02-05 3:28 ` Matt Turner
2014-02-05 5:41 ` Tom Wijsman
2014-02-05 11:41 ` Sergey Popov
2014-02-05 11:58 ` Jeroen Roovers
2014-02-05 12:58 ` Tom Wijsman
2014-02-05 13:07 ` [gentoo-dev] " Duncan
2014-02-06 10:10 ` Tom Wijsman
2014-02-06 13:39 ` Duncan
2014-02-05 16:55 ` [gentoo-dev] " Steev Klimaszewski
2014-02-05 21:17 ` Tom Wijsman
2014-02-06 4:17 ` [gentoo-dev] " Duncan
2014-02-05 12:05 ` [gentoo-dev] " Tom Wijsman
2014-02-05 20:18 ` Peter Stuge
2014-02-05 21:23 ` [gentoo-dev] [OT] " Tom Wijsman
2014-02-05 4:55 ` [gentoo-dev] " Tom Wijsman
2014-02-05 16:07 ` Steev Klimaszewski
2014-02-05 21:48 ` Tom Wijsman
2014-02-05 22:05 ` Rick "Zero_Chaos" Farina
2014-02-06 0:48 ` Tom Wijsman
2014-02-06 1:00 ` Rick "Zero_Chaos" Farina
2014-02-06 1:50 ` Rich Freeman
2014-02-06 2:50 ` Tom Wijsman
2014-02-06 3:24 ` Chris Reffett
2014-02-06 1:51 ` Tom Wijsman
2014-02-06 3:04 ` Tyler Pohl
2014-02-06 3:12 ` Tom Wijsman
2014-02-06 18:26 ` William Hubbs
2014-02-06 19:50 ` [gentoo-dev] " Duncan
2014-02-06 2:12 ` [gentoo-dev] " Jeroen Roovers
2014-02-06 2:53 ` Tom Wijsman
2014-02-06 5:21 ` [gentoo-dev] " Duncan
2014-02-06 6:11 ` [gentoo-dev] [OT] " Tom Wijsman
2014-02-06 8:47 ` Peter Stuge
2014-02-06 10:03 ` Tom Wijsman
2014-02-06 10:37 ` Peter Stuge
2014-02-05 10:52 ` [gentoo-dev] " Rich Freeman
2014-02-05 16:26 ` Steev Klimaszewski
2014-02-05 21:50 ` Tom Wijsman
2014-02-05 22:03 ` Ciaran McCreesh
2014-02-06 0:57 ` Tom Wijsman
2014-02-13 21:28 ` [gentoo-dev] " Steven J. Long
2014-02-14 18:59 ` Tom Wijsman
2014-02-15 0:28 ` Assigning keyword/stable bugs to arch teams (WAS: [gentoo-dev] dropping redundant stable keywords) Jeroen Roovers
2014-02-15 10:41 ` Tom Wijsman
2014-02-15 13:30 ` Jeroen Roovers
2014-02-15 13:43 ` Pacho Ramos
2014-02-15 15:18 ` Rich Freeman
2014-02-16 7:41 ` Tom Wijsman
2014-02-15 23:05 ` William Hubbs
2014-02-16 7:23 ` Tom Wijsman
2014-02-16 13:48 ` Jeroen Roovers
2014-02-16 14:22 ` Rich Freeman
2014-02-16 14:31 ` Jeroen Roovers
2014-02-16 14:38 ` Rich Freeman
2014-02-16 14:58 ` Jeroen Roovers
2014-02-16 17:41 ` William Hubbs
2014-02-16 17:29 ` Tom Wijsman
2014-02-15 22:53 ` William Hubbs
2014-02-15 23:37 ` Jeroen Roovers
2014-02-16 1:05 ` William Hubbs
2014-02-16 8:05 ` Tom Wijsman
2014-02-16 8:00 ` Tom Wijsman
2014-02-16 14:04 ` Jeroen Roovers
2014-02-16 17:48 ` Tom Wijsman
2014-02-16 8:41 ` Pacho Ramos
2014-02-16 14:03 ` Rich Freeman
2014-02-16 14:18 ` Pacho Ramos
2014-02-16 14:46 ` Jeroen Roovers
2014-02-16 14:53 ` Pacho Ramos
2014-02-16 15:08 ` Jeroen Roovers
2014-02-16 18:09 ` Tom Wijsman
2014-02-16 14:26 ` Jeroen Roovers
2014-02-17 1:49 ` Steev Klimaszewski
2014-02-16 17:58 ` Tom Wijsman
2014-02-16 20:50 ` William Hubbs
2014-02-17 18:46 ` Tom Wijsman
2014-02-17 20:47 ` Jeroen Roovers
2014-02-17 23:41 ` Tom Wijsman
2014-02-16 7:45 ` Tom Wijsman
2014-02-18 18:31 ` [gentoo-dev] Re: dropping redundant stable keywords Steven J. Long
2014-02-18 21:10 ` Tom Wijsman
2014-02-18 21:16 ` Ciaran McCreesh
2014-02-18 21:42 ` Tom Wijsman
2014-01-30 8:27 ` [gentoo-dev] " Sergey Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140205010833.1bcf8dca@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=slong@rathaus.eclipse.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox