1 |
On Tue, Nov 30, 2021 at 9:59 AM Matt Connell (Gmail) |
2 |
<matthewdconnell@×××××.com> wrote: |
3 |
> |
4 |
> On Tue, 2021-11-30 at 09:18 -0500, Rich Freeman wrote: |
5 |
> > A little background for the curious, and I'll just try to stick to the |
6 |
> > factual narrative and what the main opinions are: |
7 |
> |
8 |
> Gentoo is in an awkward position here: as was discussed in the bug, it |
9 |
> isn't simply a matter of setting libpng[-apng] by default, letting |
10 |
> Mozilla bundle their own libpng, and moving on with life. Other |
11 |
> programs on Gentoo systems, built against libpng over the years with |
12 |
> apng support, will suddenly *not* have it, and this situation could |
13 |
> cause problems and data loss for users. |
14 |
> |
15 |
|
16 |
So now we're getting more into personal opinion. Those same users |
17 |
will suffer data loss if they open the same files on any other linux |
18 |
distro or likely windows/OSX/etc versions of the same software, |
19 |
because they don't use the patched version of libpng. I certainly |
20 |
don't have any objection to a heads-up news item when the change hits, |
21 |
but do we REALLY want to package system libraries that have behavior |
22 |
that is unique to Gentoo, and not the same as even what the upstream |
23 |
devs expect? |
24 |
|
25 |
We had a similar situation when it came out that our version of an |
26 |
Etherium client (I think that was it) had some custom patches by |
27 |
default, which were eventually turned off by default. The patches |
28 |
were somewhat controversial, and while I think anybody should be free |
29 |
to use them (they didn't create compatibility issues with the |
30 |
blockchain per se), it is surprising behavior. This is the same |
31 |
reason that we don't go putting affiliate links into search boxes on |
32 |
our browsers like many distros do (which can be a significant source |
33 |
of revenue). Sure, we could patch our browsers to basically give |
34 |
Gentoo a small cut anytime a user searches for anything, or charge |
35 |
search engines to be the default in all our packaged browsers, but it |
36 |
just isn't the way we normally do things (and those changes are IMO |
37 |
more transparent anway - at least the affiliate links are). |
38 |
|
39 |
Now, if somebody wants to run that patch by upstream libpng and it |
40 |
shows signs of getting accepted then by all means hold off until that |
41 |
is settled. The goal is to stick to upstream, and we can always |
42 |
release the change ahead of them (in this case more than a decade |
43 |
ahead of them). |
44 |
|
45 |
Really though this issue has been going on forever so there is no |
46 |
reason to go breaking stuff until a final decision is made and we can |
47 |
do an orderly transition. I think the change is a good one, but it |
48 |
would have been a good one in 2010 too. |
49 |
|
50 |
-- |
51 |
Rich |