From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 659ef6bffcd217994842073ef051a6aaf9141083
Date: Sat, 26 Nov 2016 12:40:48 +0000 [thread overview]
Message-ID: <20161126124049.5C3E21078E80@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2590 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 659ef6bffcd217994842073ef051a6aaf9141083 (commit)
from c0f84b30fafdf0f5beabcdaddecb6d6795aee630 (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 659ef6bffcd217994842073ef051a6aaf9141083
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Nov 26 12:39:56 2016 +0000
ddrescue: New package
ddrescue is a data recovery tool
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
ddrescue/ddrescue.nm | 45 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
create mode 100644 ddrescue/ddrescue.nm
Difference in files:
diff --git a/ddrescue/ddrescue.nm b/ddrescue/ddrescue.nm
new file mode 100644
index 0000000..be34d02
--- /dev/null
+++ b/ddrescue/ddrescue.nm
@@ -0,0 +1,45 @@
+###############################################################################
+# IPFire.org - An Open Source Firewall Solution #
+# Copyright (C) - IPFire Development Team <info(a)ipfire.org> #
+###############################################################################
+
+name = ddrescue
+version = 1.21
+release = 1
+
+groups = System/Tools
+url = http://gnu.org/software/ddrescue
+license = GPLv2+
+summary = Data recovery tool
+
+description
+ GNU ddrescue is a data recovery tool. It copies data from one file or
+ block device (hard disc, cdrom, etc) to another, trying to rescue the
+ good parts first in case of read errors.
+end
+
+source_dl = http://ftp.gnu.org/gnu/ddrescue/
+sources = %{thisapp}.tar.lz
+
+build
+ # ddrescue comes with a non-traditional configure script
+ configure_options = \
+ --prefix=%{prefix} \
+ --enable-linux \
+ CPPFLAGS="%{CPPFLAGS}" \
+ CFLAGS="%{CFLAGS}" \
+ LDFLAGS="%{LDFLAGS}" \
+ CXXFLAGS="%{CXXFLAGS}"
+
+ test
+ make check
+ end
+end
+
+packages
+ package %{name}
+
+ package %{name}-debuginfo
+ template DEBUGINFO
+ end
+end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-11-26 12:40 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=20161126124049.5C3E21078E80@git01.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