Portability links in library and development packages?

["Jens Peter Secher" <jps@debian.org>]

Let us say I have packages libfoo++1 and libfoo++-dev which make standard files

/usr/lib/libfoo++.so.1.0.0
/usr/lib/libfoo++.so.1 -> libfoo++.so.1.0.0

and

/usr/lib/libfoo++.a
/usr/lib/libfoo++.la
/usr/lib/libfoo++.so --> libfoo++.so.1.0.0
/usr/include/foo++/

Now, in some other distributions, these files are called foopp instead
of foo++, and so to aid portability of client code, I put in the
additional following links.

/usr/lib/libfoopp.so.1 -> libfoo++.so.1

and

/usr/lib/libfoopp.a --> libfoo++.a
/usr/lib/libfoopp.la --> libfoo++.a
/usr/lib/libfoopp.so --> libfoo++.so
/usr/include/foopp --> foo++

I have a funny feeling that such links could break something, but I
cannot find a case where it actually does.  Can any of you?


Cheers,
-- 
                                                    Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?