1 |
On Fri, Sep 23, 2011 at 5:44 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
2 |
> I believe something needs to be done with the zlib-1.2.5.1-r1 and -r2 |
3 |
> packages currently in the tree. The maintainer of zlib pushed those |
4 |
> revisions with a patch that alters macro identifiers, making Gentoo's zlib |
5 |
> incompatible with upstream. As a result, a lot of packages stopped |
6 |
> building. Bug reports for broken packages come in and then are being |
7 |
> modified to fit Gentoo's zlib. |
8 |
> |
9 |
> Breaking compatibility with upstream zlib also means that non-portage |
10 |
> software, the ones I install with "./configure --prefix=$HOME/usr && make |
11 |
> install", also won't build. |
12 |
> |
13 |
> It's a mess right now and it just doesn't look right. The bug that deals |
14 |
> with it was locked from public view: |
15 |
> |
16 |
> https://bugs.gentoo.org/show_bug.cgi?id=383179 |
17 |
> |
18 |
> Is there a plan for this, or will we have to live with what is essentially |
19 |
> an incompatible Gentoo fork of zlib? |
20 |
|
21 |
It seemed to me like this was a silly problem from the outset. vapier |
22 |
did arguably the right thing, and if that means exposing some broken |
23 |
software, fine. We handle plenty of breakage worse than this, but I |
24 |
understand that it can be inconvenient. |
25 |
|
26 |
However, you completely lost any support when you said |
27 |
|
28 |
> Yes, bad idea. But it's in my liberty to write code however I see fit. |
29 |
|
30 |
That just makes me want to slap you. |
31 |
|
32 |
I'll echo what vapier said in response: it's absolutely your |
33 |
prerogative to do whatever you want, but it's not our responsibility |
34 |
to make sure that it works in Gentoo. |
35 |
|
36 |
> It's a bad call. You've made plenty of those lately. This is just another one. |
37 |
> IMO, you don't have the skills and insight to mess with this stuff. So when you |
38 |
> try, breakage happens. I hope you retire soon. |
39 |
|
40 |
Are you kidding me? Grow up. |