[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Namespace-Conflict /usr/include/netatalk/at.h
From: |
Andreas Jaeger |
Subject: |
Re: Namespace-Conflict /usr/include/netatalk/at.h |
Date: |
25 May 2001 09:42:30 +0200 |
User-agent: |
Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Channel Islands) |
Sebastian Rittau <address@hidden> writes:
> [NB: Please reply to both mailing lists mentioned in the To header.
> If I mailed to the wrong glibc mailing list, please reply to the
> right one.]
>
> Hi!
>
> I'm the maintainer of the Debian netatalk package. I noticed a conflict
> between glibc2 and netatalk (currently at 1.5pre6). Both packages try
> to install a file called /usr/include/netatalk/at.h. While the glibc
> version just contains some #includes and a #define of SOL_ATALK, the
> netatalk version contains a lot of #defines and struct definitions.
The glibc header is needed. Compare what the headers actually do, the
netatalk header is basically:
#ifdef linux /* pull in the linux header */
#include <sys/socket.h>
#include <asm/types.h>
#include <linux/atalk.h>
#else
...
#endif
and the glibc one:
#include <asm/types.h>
#include <linux/atalk.h>
#include <sys/socket.h>
#define SOL_ATALK 258 /* sockopt level for atalk */
> I think, we need a solution to that conflict. The simple way is to
> move this file away in glibc, but I don't know if this possible
> without breaking anything. Of course, netatalk could just #define
> SOL_ATALK in its header file (or #include a new file in glibc that
> contains this definition), but this would require any user of that
> define to install netatalk. Another solution is to include
> netatalk's version of the file in the glibc distribution, but that
> would cause maintainance problems.
The solution is to not install the netatalk version at all.
Andreas
--
Andreas Jaeger
SuSE Labs address@hidden
private address@hidden
http://www.suse.de/~aj