On Sat, 2006-04-29 at 11:10 +0100, Joe Orton wrote:
> On Fri, Apr 28, 2006 at 02:23:48PM -0400, Jeremy Katz wrote:
> > What does this mean to you as a package maintainer? In a lot of cases,
> > hopefully nothing. But there are cases where header files included in
> > packages are generated at build-time and have an architecture or build
> > specific nature. These conflicts will need to be fixed similar to how
> > things have been fixed for runtime library issues -- either moving files
> > around or removing the cause for the difference. If there is a valid
> > reason for them to be different, then you might want to explore having a
> > common stub header that includes the different headers as appropriate
> > (eg, how /usr/include/gnu/stubs.h is handled)
>
> Nobody has come up with a feasible plan for dealing with
> %{_bindir}/foo-config scripts AFAIK.
Probably the best thing to do in these cases is to create pkgconfig .pc
files and then make the foo-config script a simple wrapper around
pkgconfig.
Jeremy
