1 |
On śro, 2017-05-31 at 14:19 +0200, Sebastian Pipping wrote: |
2 |
> Hi! |
3 |
> |
4 |
> |
5 |
> The next release of dev-libs/expat is not far away and there are two |
6 |
> things that I would appreciate input with, before the next bump in Gentoo: |
7 |
> |
8 |
> |
9 |
> -DXML_UNICODE_WCHAR_T issues and Gentoo/Debian mismatch |
10 |
> ======================================================= |
11 |
> |
12 |
> With USE=unicode, on Gentoo two extra libraries are built: |
13 |
> |
14 |
> * libexpatu.so (with CPPFLAGS=-DXML_UNICODE) |
15 |
> * libexpatw.so (with CPPFLAGS=-DXML_UNICODE_WCHAR_T) |
16 |
> ^ |
17 |
> However, -DXML_UNICODE_WCHAR_T has only ever worked with 2-byte wchar_t, |
18 |
> while 4-byte wchar_t seems mainstream on Linux (and GCC -fshort-wchar |
19 |
> would required libc to have the same, if you actually wanted to pass |
20 |
> those wchar_t strings to wprintf and friends). |
21 |
> |
22 |
> So libexpatw.so in Gentoo is not functional at the moment. |
23 |
> |
24 |
> To make things worse, Debian has libexpatw.so with |
25 |
> CPPFLAGS=-DXML_UNICODE, which corresponds to current libexpatu.so in |
26 |
> Gentoo, rather than libexpatw.so. |
27 |
> |
28 |
> |
29 |
> How do you evaluate these options: |
30 |
> |
31 |
> a) Keep libexpatu.so + change libexpatw.so to CPPFLAGS=-DXML_UNICODE |
32 |
> |
33 |
> b) Drop libexpatu.so + change libexpatw.so to CPPFLAGS=-DXML_UNICODE |
34 |
|
35 |
Does any other distribution use libexpatu.so? If not, then there's |
36 |
probably no point in keeping it. |
37 |
|
38 |
> |
39 |
> |
40 |
> Depend on dev-libs/libbsd |
41 |
> ========================= |
42 |
> |
43 |
> The next release is very likely to add (optional but helpful) support |
44 |
> for arc4random_buf that dev-libs/libbsd provides (especially on systems |
45 |
> with glibc prior to 2.25) [1]. I wonder if Expat's proximity to @system |
46 |
> has any strong implications on whether |
47 |
> |
48 |
> A) libbsd should be a default-off use dependency |
49 |
> IUSE="libbsd" RDEPEND="libbsd? ( dev-libs/libbsd )" |
50 |
> |
51 |
> B) libbsd could be a default-on use dependency |
52 |
> IUSE="+libbsd" RDEPEND="libbsd? ( dev-libs/libbsd )" |
53 |
|
54 |
I'd dare say the feature is 'arc4random', then that should be the name |
55 |
of the flag. |
56 |
|
57 |
> C) libbsd could even go into DEPEND and RDEPEND directly, or |
58 |
> RDEPEND="dev-libs/libbsd" |
59 |
> |
60 |
> D) libbsd should not become any kind of future dependency of |
61 |
> dev-libs/expat. |
62 |
> |
63 |
|
64 |
-- |
65 |
Best regards, |
66 |
Michał Górny |