> 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 drawing figures. It relies on a shared library
which it is essentially the only package to use, but can be used to
extend it through plugins ('ipelets'). There are headers associated to
it, which I will of course put in ipe7-dev. A plugin package would
depend on the ipe7-shlibs package and build-depend on ipe7-dev (and the
plugin would be very likely to need deep rewriting should the major
version ever increase).
/v
--
Vincent Beffara
UMPA - ENS-Lyon
46 allée d'Italie
69364 Lyon Cedex 07
Tél : 04 72 72 85 25
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
