This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: IDN support in getaddrinfo().

Hash: SHA1

Simon Josefsson wrote:

> I'm a little confused, earlier you said to use read, but I don't know
> how `read' could be used on a DSO to get something useful out of it.
> Should I create a DSO and use dlopen on it?  It was quite some time
> since I last used dlopen, but I'll see if I can get it to work...

Do whatever is simplest.  Using a DSO  has the advantage that no fixed
offset references are needed.  In other parts of glibc we use normal
data files and have special headers at the front identifying the various
part.  Using this approach is faster.  It only gets complicated if the
data consists of many different parts.

> The approach I'm considering is to take the current libc libidn
> "add-on" package but change the Versions file so it only export the
> necessary APIs in a GLIBC_PRIVATE block.  Any problems with this?  The
> alternative approach I see is to move everything into sysdeps/posix
> (or somewhere), but that doesn't seem as clean.

We could keep it as a separate add-on.  This would be of benefit if you
want to continue distributing the same code base separately.  I'm no big
fan of this.  I'd prefer an integration into glibc proper.  Maybe adding
the code in a subdir (posix/idn, no need to more it to sysdeps).

- -- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
Version: GnuPG v1.2.3 (GNU/Linux)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]