Re: RFC: How to organize guile-gnome

[Greg Troxel]

  I don't know how NetBSD pkgsrc works, but in Debian you can have one
  source package creating multiple binary packages, which then show the
  above dependencies.

This is a cool feature, but pkgsrc unfortunately doesn't have it.  The
basic approach is to build a package, install all or some of it, and
then package up the resulting installed files.  Thus my plea for the
ability to install in chunks (rather than everything up to and
including some point).

  Build-dependencies are only an issue for developers, who normally
  don't care about a few -dev packages more or less.

sure, I am worrying about run-time stuff, for example needing
glib-2.0.so.  It's more that as this grows the list of things you need
to build it all will get huge, so the approach of making one package
which has all the bindings makes that package have tons of dependencies.

BTW NetBSD pkgsrc does not split up packages into -dev (arguably this
is lame of it); when you install glib-1.2.10, for example, you get

  bin/glib-config
  include/glib/glib-1.2/glib.h
  include/glib/glib-1.2/gmodule.h
  info/glib.info
  lib/glib/include/glibconfig.h
  lib/libglib.a
  lib/libglib.la
  lib/libglib.so
  lib/libglib.so.13
  lib/libglib.so.13.10
  lib/libgmodule.a
  lib/libgmodule.la
  lib/libgmodule.so
  lib/libgmodule.so.13
  lib/libgmodule.so.13.10
  lib/libgthread.a
  lib/libgthread.la
  lib/libgthread.so
  lib/libgthread.so.13
  lib/libgthread.so.13.10
  lib/pkgconfig/glib.pc
  lib/pkgconfig/gmodule.pc
  lib/pkgconfig/gthread.pc
  man/man1/glib-config.1
  share/aclocal/glib.m4

I suppose only the .so versions would be in the base package, with the
rest in -dev, and this would be nice.  This would be painful to do
without the 'one pkgsrc directory creates multiple packages' notion,
though.

    Greg