PSARC/2008/072 - Including LibMNG with Solaris

[James Carlson]

John Fischer writes:
> 	/usr/lib/libmng.so.1.0.0
> 	/usr/lib/libmng.so.1 -> /usr/lib/libmng.so.1.0.0
> 	/usr/lib/libmng.so -> /usr/lib/libmng.so.1.0.0

Same library versioning questions here.  This doesn't look right to
me.

> 	By default, LibMNG installs its header files under /usr/include.
> 	We propose changing this default installation location to a more
> 	suitable /usr/include/libmng, for the purpose of avoiding namespace
> 	pollution in /usr/include.

This doesn't use pkgconfig, right?  How do applications find the
include files that we've moved around?  Should we be using a
non-default location if it potentially causes trouble for third-party
software?

> 	LibMNG's development and release schedule are controlled by a group
> 	of developers external to SMI [1]. Although the MNG Specification [2]
> 	is 'frozen', and LibMNG attempts to maintain API and ABI compatibility
> 	between Major release versions, no explicit compatibility guarantees
> 	are provided by LibMNG.

Same stability comments as the other case.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677