building a standalone rpm from the standalone tarball
This allows the rpm to be built anywhere the necessary build deps are available (including on debian) and the resulting package will work on as broad a range of rpm distributions as the libc/kernel supports. The DistributionUpdate changes to use the new script have not yet been tested.
This commit is contained in:
parent
53fd746705
commit
4508198507
5 changed files with 121 additions and 4 deletions
44
standalone/rpm/git-annex-standalone.spec
Normal file
44
standalone/rpm/git-annex-standalone.spec
Normal file
|
@ -0,0 +1,44 @@
|
|||
Name: git-annex-standalone
|
||||
Version: %{version}
|
||||
Release: %{release}
|
||||
Summary: manage files with git, without checking their contents into git
|
||||
License: AGPL
|
||||
AutoReqProv: no
|
||||
Requires: git
|
||||
|
||||
%description
|
||||
git-annex allows managing files with git, without checking the file
|
||||
contents into git. While that may seem paradoxical, it is useful when
|
||||
dealing with files larger than git can currently easily handle, whether due
|
||||
to limitations in memory, time, or disk space.
|
||||
|
||||
It can store large files in many places, from local hard drives, to a
|
||||
large number of cloud storage services, including S3, WebDAV,
|
||||
and rsync, with a dozen cloud storage providers usable via plugins.
|
||||
Files can be stored encrypted with gpg, so that the cloud storage
|
||||
provider cannot see your data. git-annex keeps track of where each file
|
||||
is stored, so it knows how many copies are available, and has many
|
||||
facilities to ensure your data is preserved.
|
||||
|
||||
git-annex can also be used to keep a folder in sync between computers,
|
||||
noticing when files are changed, and automatically committing them
|
||||
to git and transferring them to other computers. The git-annex webapp
|
||||
makes it easy to set up and use git-annex this way.
|
||||
|
||||
%build
|
||||
# Need to have run make linuxstandalone (or untarred the standalone
|
||||
# tarball) before building this rpm; the git-annex source code is not built
|
||||
# here. --build-root has to be pointed at the git-annex.linux directory.
|
||||
|
||||
%install
|
||||
mkdir -p %{buildroot}/usr/lib/
|
||||
cp -a %{buildroot}/../git-annex.linux %{buildroot}/usr/lib
|
||||
mkdir -p %{buildroot}/usr/bin/
|
||||
ln -sf /usr/lib/git-annex.linux/git-annex %{buildroot}/usr/bin/git-annex
|
||||
ln -sf /usr/lib/git-annex.linux/git-annex %{buildroot}/usr/bin/git-annex-shell
|
||||
|
||||
%files
|
||||
%attr(-, root, root)
|
||||
/usr/bin/git-annex
|
||||
/usr/bin/git-annex-shell
|
||||
/usr/lib/git-annex.linux
|
38
standalone/rpm/rpmbuild-from-standalone-tarball
Executable file
38
standalone/rpm/rpmbuild-from-standalone-tarball
Executable file
|
@ -0,0 +1,38 @@
|
|||
#!/bin/sh
|
||||
# Create a standalone rpm from a standalone tarball.
|
||||
#
|
||||
# This can build a rpm for any architecture you have a standalone tarball
|
||||
# for, and does not need to be run on a machine of the same architecture.
|
||||
set -e
|
||||
rpmarch="$1"
|
||||
tarball="$2"
|
||||
version="$(echo "$3" | sed 's/-.*//')"
|
||||
release=1
|
||||
rpmrepo="$4"
|
||||
if [ -z "$rpmarch" ] || [ -z "$tarball" ] || [ -z "$version" ] || [ -z "$rpmrepo" ]; then
|
||||
echo "usage: rpmbuild-from-standalone-tarball rpmarch file.tar.gz version rpmrepo"
|
||||
fi
|
||||
|
||||
basedir="$(dirname "$0")"
|
||||
|
||||
tmpdir=$(mktemp -d)
|
||||
trap cleanup exit
|
||||
cleanup () {
|
||||
rm -rf "$tmpdir"
|
||||
}
|
||||
|
||||
cat "$tarball" | (cd "$tmpdir" && tar zx)
|
||||
buildroot="$tmpdir/rpmbuild"
|
||||
mkdir -p "$buildroot"
|
||||
|
||||
rpmbuild \
|
||||
--buildroot="$buildroot" \
|
||||
--define="_rpmdir `pwd`" \
|
||||
--define="_rpmfilename git-annex-standalone.rpm" \
|
||||
--define="version $version" \
|
||||
--define="release $release" \
|
||||
--target="$rpmarch" \
|
||||
-bb "$basedir/git-annex-standalone.spec" \
|
||||
--quiet
|
||||
package="git-annex-standalone-$version-$release.$rpmarch.rpm"
|
||||
mv git-annex-standalone.rpm "$rpmrepo/$package"
|
Loading…
Add table
Add a link
Reference in a new issue