My main concern in this thread, is that I don't want anything swept under
the rug in such a way that a wider issue is masked that actually needs
dealt with anyway.
Examples:
* A workaround to deal with a bug, especially one filed on b.g.o
- What happens if/when the bug gets fixed? Won't the wor
On 10/17/2016 06:09 AM, Raymond Jennings wrote:
> My biggest opinion regarding workarounds and bugs, is that we're
> sweeping things under the rug that should at least be documented, and
> perhaps fixed...or even punted upstream if its serious enough.
>
> Changing the status quo may require some
On Monday, October 17, 2016 9:23:09 AM EDT Michał Górny wrote:
>
> Example: udev people had problems with MULTILIB_WRAPPED_HEADERS
> in the past. Instead of contacting me (which would result in helpful
> explanation how to do things properly), they abused bash to disable
> the check function implic
On 17/10/16 03:23 AM, Michał Górny wrote:
> Hello, everyone.
>
> I'd like to point out a major problem in Gentoo: there's a fair number
> of developers who add various local workarounds to problems they meet
> and don't bother to report a bug. Worst than that, this applies not
> only for upstream
My personal opinion:
If you have to work around it, its already a bug.
On Monday 17 October 2016 09:23:09 Michał Górny wrote:
> Hello, everyone.
Hello.
Coacher's here.
> Example 2: Coacher had problem with git-r3 not trying fallback URIs
> when earlier URI was https and https wasn't supported in git. So he
> reordered URIs to have https last. With tiny explanation
On Mon, Oct 17, 2016 at 9:09 AM, Raymond Jennings wrote:
>
> Changing the status quo may require some adjustment though, but I suppose we
> could start by openly documenting a bug if we find a workaround that does
> not already have a bug number associated with it. I've seen several ebuilds
> whe
My biggest opinion regarding workarounds and bugs, is that we're sweeping
things under the rug that should at least be documented, and perhaps
fixed...or even punted upstream if its serious enough.
Changing the status quo may require some adjustment though, but I suppose
we could start by openly
On 17/10/2016 12:42, Patrice Clement wrote:
> We don't need yet another policy to "fix" two problems you've
> encountered
+1 ; policies don't always fix things
It's a worthwhile guideline though - as Gentoo devs, and maybe even
wider community, we should work together to fix problems.
That's one
Monday 17 Oct 2016 09:23:09, Michał Górny wrote :
> Hello, everyone.
>
> I'd like to point out a major problem in Gentoo: there's a fair number
> of developers who add various local workarounds to problems they meet
> and don't bother to report a bug. Worst than that, this applies not
> only for u
On Mon, Oct 17, 2016 at 12:23 AM, Michał Górny wrote:
> Hello, everyone.
>
> I'd like to point out a major problem in Gentoo: there's a fair number
> of developers who add various local workarounds to problems they meet
> and don't bother to report a bug. Worst than that, this applies not
> only
On Mon, 17 Oct 2016 09:23:09 +0200
Michał Górny wrote:
> Therefore, I'd like to request establishing an official policy against
> workarounds with no associated bug reports.
>
> Your thoughts?
Obviously I assume this is still a "to taste" thing, because when
you're packaging something, and you
Hello, everyone.
I'd like to point out a major problem in Gentoo: there's a fair number
of developers who add various local workarounds to problems they meet
and don't bother to report a bug. Worst than that, this applies not
only for upstream problems but also to Gentoo eclass/ebuild-related
issu
13 matches
Mail list logo
