1 |
On Saturday 31 May 2008 11:14:33 Luca Barbato wrote: |
2 |
> Ciaran McCreesh wrote: |
3 |
> > Fact: the underlying issue is a libtool bug. |
4 |
> |
5 |
> Wrong, it isn't just that, --as-needed and libtool are unrelated. |
6 |
|
7 |
The issue that as-needed tries to solve is libraries being linked to binaries |
8 |
or other libraries that don't use said library directly. While it's true |
9 |
that libtool isn't the only cause, it does produce by far the most. |
10 |
|
11 |
> > Fact: as-needed does not fix this bug. It attempts to work around it. |
12 |
> |
13 |
> Wrong, --as-needed does exactly what is supposed to do, precise |
14 |
> bookkeeping. |
15 |
|
16 |
It does do what it's supposed to do, unfortunately "what it's supposed to do" |
17 |
isn't the right thing in all cases. And it's not "precise", it simply uses a |
18 |
different criterion that's better in some cases and worse in others. |
19 |
|
20 |
> > Fact: as-needed breaks standard-compliant code. |
21 |
> |
22 |
> Wrong, --as-needed breaks disputable code that happens to be |
23 |
> standard-compliant by a specific read of the standard. The fact the |
24 |
> specific code is something wrong from the security/style/maintainability |
25 |
> point makes it a bonus. |
26 |
|
27 |
No-one's given any reason why it's "disputable", worse "style" or |
28 |
less "maintainable", other than "it doesn't work with --as-needed", quite a |
29 |
circular argument. As for "security"... please show evidence, or I'll have |
30 |
to assume that that's just desperate FUD. |
31 |
|
32 |
> > Fact: fixing the libtool bug would give all the benefits purportedly |
33 |
> > given by using as-needed, without the drawbacks. |
34 |
> |
35 |
> Wrong, fixing libtool gives other benefits, so it's worth trying to fix |
36 |
> it as well. The new autotools and proper usage of them makes life easier |
37 |
> so it's worth improving on this side. |
38 |
|
39 |
I really don't see what you're trying to say there.... |
40 |
-- |
41 |
gentoo-dev@l.g.o mailing list |