Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Alec Warner <antarus@g.o>
Subject: Re: Re: zlib breakage
Date: Fri, 23 Sep 2011 16:40:06 -0700
On Fri, Sep 23, 2011 at 4:26 PM, Nikos Chantziaras <realnc@...> wrote:
> On 09/24/2011 02:10 AM, Matt Turner wrote:
>>
>> On Fri, Sep 23, 2011 at 5:44 PM, Nikos Chantziaras<realnc@...>
>>  wrote:
>>>
>>> I believe something needs to be done with the zlib-1.2.5.1-r1 and -r2
>>> packages currently in the tree.  The maintainer of zlib pushed those
>>> revisions with a patch that alters macro identifiers, making Gentoo's
>>> zlib
>>> incompatible with upstream.  As a result, a lot of packages stopped
>>> building.  Bug reports for broken packages come in and then are being
>>> modified to fit Gentoo's zlib.
>>>
>>> Breaking compatibility with upstream zlib also means that non-portage
>>> software, the ones I install with "./configure --prefix=$HOME/usr&&  make
>>> install", also won't build.
>>> [...]
>>
>> It seemed to me like this was a silly problem from the outset. vapier
>> did arguably the right thing, and if that means exposing some broken
>> software, fine. We handle plenty of breakage worse than this, but I
>> understand that it can be inconvenient.
>>
>> However, you completely lost any support when you said
>>
>>> Yes, bad idea.  But it's in my liberty to write code however I see fit.
>>
>> That just makes me want to slap you.
>>
>> I'll echo what vapier said in response: it's absolutely your
>> prerogative to do whatever you want, but it's not our responsibility
>> to make sure that it works in Gentoo.
>
> The code is perfectly valid.  You cannot force people to follow your coding
> standards.  If it's valid C code, it doesn't matter that it contradicts your
> personal preferences.  It's not your code and you don't have a saying in it.
>  What's next, banning software that indents code with tabs instead of
> spaces?

You are allowed to disagree with his changes; but that doesn't mean we
must listen to you.
I actually disagree with Vapier as well (I don't see why we would act
without waiting for upstream) but I also trust his technical ability
in matters like this.

>
>
>>> It's a bad call. You've made plenty of those lately. This is just another
>>> one.
>>> IMO, you don't have the skills and insight to mess with this stuff. So
>>> when you
>>> try, breakage happens. I hope you retire soon.
>>
>> Are you kidding me? Grow up.
>
> This was just another episode of Vapier's hostile and arrogant behavior
> towards users.  Every time someone comes up with a valid argument of why
> he's wrong, the final answer is "don't care, I do what I please because I'm
> the dev and you're not."  So my reply was the politest I could come up with
> without using the f-word.

I'm curious what you think the final answer should be?

-A

>
>
>


Replies:
Re: zlib breakage
-- Nikos Chantziaras
References:
zlib breakage
-- Nikos Chantziaras
Re: zlib breakage
-- Matt Turner
Re: zlib breakage
-- Nikos Chantziaras
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: zlib breakage
Next by thread:
Re: zlib breakage
Previous by date:
Re: Re: zlib breakage
Next by date:
Re: zlib breakage


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.