tags 327853 + wontfix
thanks
[Alessandro Amici]
> The changelog.Debian file gives a few reasons for not building
> libmapserver-dev, but now there is at least one client that needs
> it, and a pretty important one IMHO.
I assume you are talking about this comment in the changelog:
- Do not build libmapserver-dev any more. It can't be used without
the defines used during compilation, the ABI is not stable, and
there are no client programs using it at the moment.
As far as I know, the mapserver library API is still not stable, and
still unusable without using the exact same set of defines as used
during compilation. This mean that if I was to provide a library and
a development package, every time I changed the build rules or
upgraded, I would break all packages using this library. In addition,
the upstream have no plans for fixing the API or ABI, and do not as
far as I know handle sonames for the library.
In short, I am not willing to provide a library for use by other
packages under these conditions, as it would either make it harder for
me to upgrade the package, or give me a lot of complaints when I
upgrade and break existing packages.
I'll change my mind when upstream stabilizes the library API and
understand and accept that sonames should be handled upstream and
change every time the library ABI changes, as well as rewrite the
header file system to document the compile defines used when building
the library.
Until that time, I suggest you maintain your own mapserver package if
you want to link with the library. This way you always know how it
was compiled, and can keep track of the ABI of the library you use.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
