Hello,
The original package is named 'ipe6' because it builds shared libraries
as well (ipe6-shlibs). I'd recommend making the library package
ipe7-shlibs for consistency, but you're welcome to call the main package
ipe.
More critically, what is the install_name of the library? If it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/21/10 11:27 AM, Vincent Beffara wrote:
Hello,
The original package is named 'ipe6' because it builds shared libraries
as well (ipe6-shlibs). I'd recommend making the library package
ipe7-shlibs for consistency, but you're welcome to call
For consitstency, I chose to use libipe.7.dylib as install_name
and so ipe7-shlibs as corresponding package name. The actual
software does not really do anything about it (without a patch the
install_name ends up being ../../build/src/libipe.so.5.0.10 or
something like that).
I'd
On Sun, Mar 21, 2010 at 04:49:11PM +0100, Vincent Beffara wrote:
For consitstency, I chose to use libipe.7.dylib as install_name
and so ipe7-shlibs as corresponding package name. The actual
software does not really do anything about it (without a patch the
install_name ends up being
Ooh wait, is ipe the headers used for building against the
ipeX-shlibs package? If so, the headers package must never change
which -shlibs it's associated with. Otherwise, other packages that
want to use ipe won't be able to control or know which library they
get.
No, 'ipe' is a GUI for
On Sun, Mar 21, 2010 at 05:35:37PM +0100, Vincent Beffara wrote:
Ooh wait, is ipe the headers used for building against the
ipeX-shlibs package? If so, the headers package must never change
which -shlibs it's associated with. Otherwise, other packages that
want to use ipe won't be able to
