sure I totally understand the -shlibs and agree it's the -bin i have a
problem with, I think -bin should be the main pkg and that if need be a
-dev package with the headers and stuff (which will be optional install of
course), that would help clean up the huge include dir, since we are
implementing a change I figure we should do it all at once instead of
twice. -dev pkgs are rarely used thus making it a benifit to make it,
cutting down on installed files and wasted space. If a pkg depends on
-dev well then it must be installed but in most cases -shlibs will be
enough.
[EMAIL PROTECTED] writes:
>Hi. The most minimal form of implementing shlibs just divides the package
>in half, with pkg-shlibs containing libpkg.N.x.y.dylib, libpkg.N.dylib
>and often nothing else. (In particular, libpkg.dylib belongs in pkg,
>not pkk-shlibs.) It is OK to put /sw/share/pkg/N/* in there as well,
>so long as the major version number N occurs in the name.
>
>What will happen is that at compile time, users will have both pkg and
>pkg-shlibs installed, but at runtime, they might only have pkg-shlibs
>installed. SO, if there are userland binaries as well as libraries,
>they could be put in a separate package.
¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·.,
Justin F. Hallett
CAISnet Inc.
2nd Floor, 11635 - 160 Street
Edmonton, AB, Canada T5M 3Z3
Phone: (780)-408-3094
Fax: (780)-454-3200
E-Mail: [EMAIL PROTECTED]
http://www.caisnet.com/
¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·.,
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
