I don't disagree with the logic. But unfortunately, if you did this
for a package that already existed and that some other package already
depended on, then everybody's installations would break unless you
got all maintainers of the other packages to upgrade them at exactly
the same time you upgr
right and my suggestions is
Depends: pkg, pkg-shlibs
BuildDepends: pkg-dev
thus -dev only being needed during the build process and no one needs to
update the pkgs that depend on the lib, just add -shlibs and BuildDepend.
And it just seems more logical to me...but it's jsut a suggestion.
[EMAI
I agree that in many cases we should have three packages from pkg, and other
packages would say (using the current names):
Depends: pkg-shlibs, pkg-bin
BuildDepends: pkg
Also, pkg depends on pkg-shlibs (and maybe should also depend on pkg-bin
in some cases).
Right now, the other packages sa
ahh this helps, but why did we do this? -dev is more logical then -bin
which really should be the base pkg IMHO
[EMAIL PROTECTED] writes:
>Also, there is no pkg-dev. That is a Debian project thing, and we are
>using different names.
>
> Fink name Debian name
>pkg pkg-dev
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
implementin
Also, there is no pkg-dev. That is a Debian project thing, and we are
using different names.
Fink name Debian name
pkg pkg-dev
pkg-shlibs pkg
pkg-bin pkg-runtime
We use pkg instead of pkg-dev for a better upgrade path, since lots of
packages are alre
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 t
I heard the shlibs is your little project, i'd like to know why we decided
on -bin, I missed lots od emails when tis was discussed and sorry if i'm
rehashing out topics but to me
(current -bin + the base dylib and .a and .la)
-shlibs (current -shlibs, versioned.dylibs)
-dev (includes and the ext
