A big question is the ease of installation for those using OS package
systems vs those doing things by hand. My view is that the really big
issue is making things
a) easy to package
and
b) easy to use once packaged
Since that's what is in the critical path to having things like
gnumeric have guile support out of the box.
FWIW NetBSD pkgsrc installs libltdl via the devel/libltld package.
Do people other than guile hackers build guile by hand, and if so do
they use package systems to get things like readline and gmp?
Here's the guile control file for pkgsrc. But it seems to link in the
special guile ltldl:
/usr/pkg/bin/guile:
-lcrypt.0 => /usr/lib/libcrypt.so.0
-lm.0 => /usr/lib/libm387.so.0
-lm.0 => /usr/lib/libm.so.0
-lpthread.0 => /usr/lib/libpthread.so.0
-lguile-ltdl.1 => /usr/pkg/lib/libguile-ltdl.so.1
-lguile.12 => /usr/pkg/lib/libguile.so.12
-lc.12 => /usr/lib/libc.so.12
# $NetBSD: Makefile,v 1.58 2004/11/18 12:30:49 wiz Exp $
DISTNAME= guile-1.6.5
CATEGORIES= lang
MASTER_SITES= ${MASTER_SITE_GNU:=guile/}
MAINTAINER= [EMAIL PROTECTED]
HOMEPAGE= http://www.gnu.org/software/guile/guile.html
COMMENT= GNU's Ubiquitous Intelligent Language for Extension
CONFLICTS= guile14<1.4.1nb1 guile-oops-[0-9]*
USE_BUILDLINK3= YES
GNU_CONFIGURE= YES
USE_GNU_TOOLS+= make
USE_LIBTOOL= YES
USE_GNU_READLINE= YES
USE_MAKEINFO= YES
INFO_FILES= guile.info guile-tut.info goops.info r5rs.info
TEST_DIRS= ${WRKSRC}
TEST_TARGET= check
.include "../../mk/bsd.prefs.mk"
.if ${OPSYS} == "Darwin"
CPPFLAGS+= -Dmacosx
post-patch:
@${MV} ${WRKSRC}/guile-config/guile-config.in.orig \
${WRKSRC}/guile-config/guile-config.in
.endif
.include "../../devel/libltdl/buildlink3.mk"
.include "../../devel/ncurses/buildlink3.mk"
.include "../../devel/readline/buildlink3.mk"
.include "../../mk/pthread.buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
--
Greg Troxel <[EMAIL PROTECTED]>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
