From e5c87896bce026bcaf0583c09c5bc2ba6a709c69 Mon Sep 17 00:00:00 2001 From: Eduard Warkentin Date: Wed, 27 Dec 2006 01:04:57 +0000 Subject: Added initial ebuild of darbackup svn path=/sunrise/; revision=2497 --- app-backup/darbackup/Changelog | 64 +++++++++++++++++++++++++++++++ app-backup/darbackup/darbackup-0.7.ebuild | 24 ++++++++++++ app-backup/darbackup/metadata.xml | 5 +++ 3 files changed, 93 insertions(+) create mode 100644 app-backup/darbackup/Changelog create mode 100644 app-backup/darbackup/darbackup-0.7.ebuild create mode 100644 app-backup/darbackup/metadata.xml (limited to 'app-backup') diff --git a/app-backup/darbackup/Changelog b/app-backup/darbackup/Changelog new file mode 100644 index 000000000..a23f4e181 --- /dev/null +++ b/app-backup/darbackup/Changelog @@ -0,0 +1,64 @@ +# ChangeLog for / +# Copyright 1999-2006 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*-- (DD MMM YYYY) + + 27 Dec 2006; Eduard Warkentin : Initial import. + Ebuild submitted by Eduard Warkentin . + Note that the "changed_file" listing is optional if you are simply bumping + the rev of the ebuild and are only making changes to the .ebuild file + itself. Also note that we now have a single unified paragraph rather than + having the first line separated from the rest by a newline. Everything + should be in one block like this. (note by drobbins, 16 Jul 2002) + +-- Explanation of ChangeLog format: + + *************************************************************************** + THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all + changes made to a set of ebuilds. That means that the most recent ChangeLog + entry *always* goes at the top of the file. More explanation below. + *************************************************************************** + + *************************************************************************** + ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this + format and organize all changes under the "correct" "*" entry. This is not + correct. However, rather than making a concerted effort to fix these + ChangeLogs, we should spend our energy defining a comprehensive and strict + XML-based ChangeLog format which we then migrate to. But for any entries to + any ChangeLog that *you* make, please make sure to always add entries to the + top of the file like a good boy/girl. Even do this if it's clear that you're + adding an entry to a b0rked ChangeLog. + *************************************************************************** + + This changelog is targeted to users. This means that the comments should be + well explained and written in clean English. + + Every new version or revision of the package should be marked by a '*' + separator line as above to indicate where in the chronology it was first + added to our CVS tree. Any changes since the last revision, really _any + changes at all_ have to be added to the top of the file, underneath the + initial copyright and cvs header comments, in exactly the same format as this + comment. If you are modifying older ebuilds, simply note them as changed + files and add your entry to the top of the ChangeLog. Resist the temptation + to "organize" your ChangeLog entries by placing them under the "correct" "*" + entries -- this isn't the purpose of the "*" entries. + + This means that you start with header line that has the following format, + indented two spaces: + + DD MMM YYYY; your_name changed_file1, changed_file2: Your + explanation should follow. It should be indented and wrapped at a line width + of 80 characters. The changed_files can be omitted if they are obvious; for + example, if you are only modifying the .ebuild file and committing a new rev + of a package. Any details about what exactly changed in the code should be + added as a message when the changes are committed to cvs, not in this file. + +-- A word regarding credit: + + Please add credit information ("ebuild submitted by ...", "patch submitted + by ...") to the ChangeLog. Do not add this information to the ebuilds + themselves. + + And remember: Give credit where credit is due. We're all doing this for + free, so the best we can hope (and expect!) to receive is credit. diff --git a/app-backup/darbackup/darbackup-0.7.ebuild b/app-backup/darbackup/darbackup-0.7.ebuild new file mode 100644 index 000000000..31ed6b875 --- /dev/null +++ b/app-backup/darbackup/darbackup-0.7.ebuild @@ -0,0 +1,24 @@ +# Copyright 1999-2006 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: $ + +inherit subversion + +ESVN_REPO_URI="https://faracvs.cs.uni-magdeburg.de/svn/christsc/darbackup/darbackup/branches/0.7-stable" + +DESCRIPTION="a wrapper script for creating backups using dar" +HOMEPAGE="https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup/" +SRC_URI="" +IUSE="" +SLOT="0" +LICENSE="GPL-2" +KEYWORDS="~x86 ~amd64" +RDEPEND=">=app-backup/dar-2.2.6 \ +|| ( dev-util/bdelta dev-util/xdelta ) \ +net-misc/openssh" +DEPEND=">=app-shells/bash-3.0" + +src_install() { + dobin darbackup + doman darbackup.1 +} diff --git a/app-backup/darbackup/metadata.xml b/app-backup/darbackup/metadata.xml new file mode 100644 index 000000000..7e3286984 --- /dev/null +++ b/app-backup/darbackup/metadata.xml @@ -0,0 +1,5 @@ + + + +maintainer-wanted + -- cgit v1.2.3-65-gdbad