public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 6a3ef4f4993e573ee30d7bb96ebc33e70124cec5
Date: Tue, 01 Dec 2015 23:33:10 +0100	[thread overview]
Message-ID: <20151201223310.C17EE21578@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2905 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".

The branch, master has been updated
       via  6a3ef4f4993e573ee30d7bb96ebc33e70124cec5 (commit)
      from  b57a0ea8deb6dd3b71761ffc05acc7eab28fb0c6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6a3ef4f4993e573ee30d7bb96ebc33e70124cec5
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Dec 1 22:32:43 2015 +0000

    compat-isl: Add compat package because of soname bump in isl
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 isl/isl.nm => compat-isl/compat-isl.nm | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)
 copy isl/isl.nm => compat-isl/compat-isl.nm (77%)

Difference in files:
diff --git a/compat-isl/compat-isl.nm b/compat-isl/compat-isl.nm
new file mode 100644
index 0000000..39cd5ec
--- /dev/null
+++ b/compat-isl/compat-isl.nm
@@ -0,0 +1,52 @@
+###############################################################################
+# IPFire.org    - An Open Source Firewall Solution                            #
+# Copyright (C) - IPFire Development Team <info(a)ipfire.org>                   #
+###############################################################################
+
+name       = compat-isl
+version    = 0.12.2
+release    = 1
+thisapp    = isl-%{version}
+
+groups     = System/Libraries
+url        = http://isl.gforge.inria.fr/
+license    = MIT
+summary    = Integer Set Library
+
+description
+	isl is a library for manipulating sets and relations of integer points
+	bounded by linear constraints. Supported operations on sets include
+	intersection, union, set difference, emptiness check, convex hull,
+	(integer) affine hull, integer projection, computing the lexicographic
+	minimum using parametric integer programming, coalescing and parametric
+	vertex enumeration.
+end
+
+source_dl += http://isl.gforge.inria.fr/
+sources    = %{thisapp}.tar.lzma
+
+build
+	requires
+		gmp-devel
+	end
+
+	test
+		export LD_LIBRARY_PATH=$(pwd)/.libs
+		make check
+	end
+
+	install
+		# Install just the library and no headers.
+		mkdir -pv %{BUILDROOT}%{libdir}
+		install -m 644 .libs/libisl.so.10.2.2 %{BUILDROOT}%{libdir}
+		ln -svf libisl.so.10.2.2 %{BUILDROOT}%{libdir}/libisl.so.10
+	end
+end
+
+packages
+	package %{name}
+
+	package %{name}-debuginfo
+		template DEBUGINFO
+	end
+end


hooks/post-receive
--
IPFire 3.x development tree

                 reply	other threads:[~2015-12-01 22:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151201223310.C17EE21578@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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