Re: [gpsd-dev] libgps?

[Eric S. Raymond]

Bernd Zeimetz <address@hidden>:
> As mentioned before, if libgps is being statically linked, I'll
> remove gpsd from Debian. I can live with a statically linked
> libgpsd, doing so is just a waste of memory, but nothing
> problematic. Having a static libgps only means, that for every gpsd
> upload I need to get kde and all other dependencies rebuilt. That is
> nothing I will accept nor (I can't speak for them, but I'm sure
> about that fact) will the release and security teams accept such a
> broken library usage.

I think you misunderstand. The plan is *not* for there to be only
a statically-linked libgps. The shared libgps will still be exported
and third-party programs will still see it.

No, the change is to link (only) GPSD's *own* binaries with a local
static copy of libgps.  In practice this would be very low overhead,
as only about 4 libgps modules are used at the lower level for a total
code volume of about 21K.

In return, we get to deep-six the shared and chrpath build options, 
toss out all screwing around with RPATH/RUNPATH/LID_LIBRARY_PATH, 
and remove chrpath as a build requirement.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>