public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Panagiotis Christopoulos" <pchrist@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/lisp:master commit in: dev-scheme/guile/
Date: Mon,  2 Jun 2014 11:41:05 +0000 (UTC)	[thread overview]
Message-ID: <1401709246.396b573823c8a9e8d9aaedd97f4dd99b02bb0cd3.pchrist@gentoo> (raw)

commit:     396b573823c8a9e8d9aaedd97f4dd99b02bb0cd3
Author:     Panagiotis Christopoulos (pchrist) <pchrist <AT> gentoo <DOT> org>
AuthorDate: Mon Jun  2 11:40:46 2014 +0000
Commit:     Panagiotis Christopoulos <pchrist <AT> gentoo <DOT> org>
CommitDate: Mon Jun  2 11:40:46 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/lisp.git;a=commit;h=396b5738

dev-scheme/guile: pushing a guile-2.0.11 preliminary ebuld (work in progress)

---
 dev-scheme/guile/guile-2.0.11.ebuild | 56 ++++++++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)

diff --git a/dev-scheme/guile/guile-2.0.11.ebuild b/dev-scheme/guile/guile-2.0.11.ebuild
new file mode 100644
index 0000000..832e120
--- /dev/null
+++ b/dev-scheme/guile/guile-2.0.11.ebuild
@@ -0,0 +1,56 @@
+# Copyright 1999-2014 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+EAPI=5
+
+inherit eutils
+
+DESCRIPTION="Scheme interpreter. Also The GNU extension language"
+HOMEPAGE="http://www.gnu.org/software/guile/"
+SRC_URI="mirror://gnu/guile/${P}.tar.gz"
+
+LICENSE="LGPL-3+"
+SLOT="0"
+#KEYWORDS="~amd64"
+# Work in progress. No keywords.
+# TODO: 
+# 1. Emacs support 
+# 2. Testing agains revdeps
+# 3. Check file placing
+# 4. ...
+KEYWORDS=""
+IUSE="networking +regex +deprecated nls debug-malloc debug +threads static"
+
+RDEPEND="
+	dev-libs/gmp
+	virtual/libiconv
+	virtual/libintl
+	sys-devel/libtool
+	dev-libs/boehm-gc
+	dev-libs/libunistring
+	dev-libs/libffi"
+
+DEPEND="${RDEPEND}
+	virtual/pkgconfig"
+
+src_configure() {
+	econf \
+		--disable-rpath \
+		$(use_enable static) \
+		--disable-error-on-warning \
+		$(use_enable debug-malloc) \
+		$(use_enable debug guile-debug) \
+		--enable-posix \
+		$(use_enable networking) \
+		$(use_enable regex) \
+		$(use_enable deprecated) \
+		$(use_enable nls) \
+		$(use_with threads) \
+		--with-modules
+}
+
+src_install() {
+	einstall || die "einstall failed"
+	dodoc AUTHORS ChangeLog GUILE-VERSION HACKING NEWS README THANKS || die
+}


             reply	other threads:[~2014-06-02 11:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 11:41 Panagiotis Christopoulos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-01 11:12 [gentoo-commits] proj/lisp:master commit in: dev-scheme/guile/ Ulrich Müller
2022-04-01 11:12 Ulrich Müller
2019-08-31 12:09 Cyprien Nicolas
2019-08-11  9:44 Cyprien Nicolas
2019-06-22 16:51 Cyprien Nicolas
2013-04-24 21:37 Panagiotis Christopoulos
2013-04-18 13:45 Cyprien Nicolas
2013-04-15 19:51 Panagiotis Christopoulos
2013-01-26 19:07 Cyprien Nicolas
2012-09-26 21:15 Cyprien Nicolas
2012-09-26 18:56 Cyprien Nicolas
2012-08-21  8:16 Cyprien Nicolas
2012-08-21  8:16 Cyprien Nicolas
2012-05-08 14:25 Cyprien Nicolas
2011-04-12  8:29 Marijn Schouten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1401709246.396b573823c8a9e8d9aaedd97f4dd99b02bb0cd3.pchrist@gentoo \
    --to=pchrist@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox