ZeroUno ha scritto:Pensa, prima di leggere quello tra parentesi stavo rispondendo "il tuo"
Cos'ha il tuo?
Per partire da una situazione che possa essere più generale possibile e valida per tutti stavo giusto cominciando dal tuo.
eh, visto che non c'e' uno standard e che sono repository personali, ognuno fa come nella
casa delle liberta', quindi troverai le situazioni piu' disparate.
alcuni dei repository linkati non sono nemmeno di slackbuilds (come il mio sbo-templates), alcuni sono obsoleti (come il mio SBo-git), ecc. ecc.
ho paura che ti dovrai districare da solo in questa giungla
Prendo ad esempio quello di
Ben Mendis, che ha forkato quello di slackbuilds.org e fatto un branch per ogni slackbuild modificato (pero' la sincronizzazione e il rebase li fa ogni quando gli va).
Lo clono e entro nella directory col repo clonato
Codice: Seleziona tutto
$ git clone git://github.com/Sitwon/SlackBuilds.git
$ cd Slackbuilds
per vedere i branch nel repository di origine
Codice: Seleziona tutto
$ git branch -r
origin/HEAD -> origin/master
origin/batctl
origin/bumblebee
origin/libvirt-0.9.9
origin/master
origin/scala-2.9.1
il primo, origin/HEAD, e' il branch di default su github, che nel repo di Ben corrisponde a origin/master.
per vedere, ad esempio, il branch batctl, ne creo uno locale collegato a quello in origin
Codice: Seleziona tutto
$ git co -b batctl origin/batctl
Branch batctl set up to track remote branch batctl from origin.
Switched to a new branch 'batctl'
ora, in locale, sono sul branch batctl
per vedere il messaggio di log che riguarda l'ultimo commit
Codice: Seleziona tutto
$ git log -1
commit 62a9278b31b42782c8b7036d1045570408e5892a
Author: Ben Mendis <ben.mendis@gmail.com>
Date: Tue May 8 15:10:30 2012 -0400
Adding batctl - control and management utility for B.A.T.M.A.N. advanced
per vedere le differenze tra l'ultimo commit e il precedente
Codice: Seleziona tutto
$ git diff HEAD^ HEAD
diff --git a/network/batctl/README b/network/batctl/README
new file mode 100644
index 0000000..b929ca7
--- /dev/null
+++ b/network/batctl/README
@@ -0,0 +1,11 @@
+batctl (B.A.T.M.A.N. advanced control and management tool)
+
+The B.A.T.M.A.N. advanced routing protocol has been included in the
+Linux kernel since 2.6.38, however the kernel module is only part of
+of the implementation. In order to create and configure mesh networks
+using the B.A.T.M.A.N. advanced protocol you need the batctl userland
+tool.
+
+Since B.A.T.M.A.N. advanced operates on layer 2 the common diagnosis
+tools do not work as expected. To solve this, batctl provides
+alternatives for ping, traceroute, and tcpdump.
diff --git a/network/batctl/batctl.SlackBuild b/network/batctl/batctl.SlackBuild
new file mode 100644
index 0000000..f200f53
--- /dev/null
+++ b/network/batctl/batctl.SlackBuild
@@ -0,0 +1,92 @@
+#!/bin/sh
+
+# Slackware build script for batctl
+
+# Written by Ben Mendis <ben.mendis@gmail.com>
+
+PRGNAM=batctl
+VERSION=${VERSION:-2011.4.0}
+BUILD=${BUILD:-1}
+TAG=${TAG:-_SBo} # the "_SBo" is required
+
+# Automatically determine the architecture we're building on:
+if [ -z "$ARCH" ]; then
+ case "$( uname -m )" in
+ i?86) ARCH=i486 ;;
+ arm*) ARCH=arm ;;
+ # Unless $ARCH is already set, use uname -m for all other archs:
+ *) ARCH=$( uname -m ) ;;
+ esac
+fi
+
+CWD=$(pwd)
+TMP=${TMP:-/tmp/SBo} # For consistency's sake, use this
+PKG=$TMP/package-$PRGNAM
+OUTPUT=${OUTPUT:-/tmp} # Drop the package in /tmp
+
+if [ "$ARCH" = "i486" ]; then
+ SLKCFLAGS="-O2 -march=i486 -mtune=i686"
+elif [ "$ARCH" = "i686" ]; then
+ SLKCFLAGS="-O2 -march=i686 -mtune=i686"
+elif [ "$ARCH" = "x86_64" ]; then
+ SLKCFLAGS="-O2 -fPIC"
+else
+ SLKCFLAGS="-O2"
+fi
+
+set -e # Exit on most errors
+# If you prefer to do selective error checking with
+# command || exit 1
+# then that's also acceptable.
+
+rm -rf $PKG
+mkdir -p $TMP $PKG $OUTPUT
+cd $TMP
+rm -rf $PRGNAM-$VERSION
+tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
+cd $PRGNAM-$VERSION
+chown -R root:root .
+find . \
+ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
+ -exec chmod 755 {} \; -o \
+ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
+ -exec chmod 644 {} \;
+
+CFLAGS="$SLKCFLAGS" \
+CXXFLAGS="$SLKCFLAGS" \
+make
+make install PREFIX=/usr MANDIR=/usr/man DESTDIR=$PKG
+
+# Strip binaries and libraries - this can be done with 'make install-strip'
+# in many source trees, and that's usually acceptable if so, but if not,
+# use this:
+find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
+ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
+
+# Compress man pages
+# If the man pages are installed to /usr/share/man instead, you'll need to either
+# add the --mandir=/usr/man flag to configure or move them manually after the
+# make install process is run.
+find $PKG/usr/man -type f -exec gzip -9 {} \;
+for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
+
+# Copy program documentation into the package
+# The included documentation varies from one application to another, so be sure
+# to adjust your script as needed
+# Also, include the SlackBuild script in the documentation directory
+mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
+cp -a \
+ README \
+ $PKG/usr/doc/$PRGNAM-$VERSION
+cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
+
+# Copy the slack-desc (and a custom doinst.sh if necessary) into ./install
+mkdir -p $PKG/install
+cat $CWD/slack-desc > $PKG/install/slack-desc
+
+# Make the package; be sure to leave it in $OUTPUT
+# If package symlinks need to be created during install *before*
+# your custom contents of doinst.sh runs, then add the -p switch to
+# the makepkg command below -- see makepkg(8) for details
+cd $PKG
+/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
diff --git a/network/batctl/batctl.info b/network/batctl/batctl.info
new file mode 100644
index 0000000..e481fcd
--- /dev/null
+++ b/network/batctl/batctl.info
@@ -0,0 +1,10 @@
+PRGNAM="batctl"
+VERSION="2011.4.0"
+HOMEPAGE="http://www.open-mesh.org/"
+DOWNLOAD="http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.4.0.tar.gz"
+MD5SUM="325b25dbb8261f7fa19c6e1d9bfba6e1"
+DOWNLOAD_x86_64=""
+MD5SUM_x86_64=""
+MAINTAINER="Ben Mendis"
+EMAIL="ben.mendis@gmail.com"
+APPROVED=""
diff --git a/network/batctl/slack-desc b/network/batctl/slack-desc
new file mode 100644
index 0000000..bc79fae
--- /dev/null
+++ b/network/batctl/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description. Line
+# up the first '|' above the ':' following the base package name, and the '|'
+# on the right side marks the last column you can put a character in. You must
+# make exactly 11 lines for the formatting to be correct. It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+ |-----handy-ruler------------------------------------------------------|
+batctl: batctl (B.A.T.M.A.N. advanced control and management tool)
+batctl:
+batctl: The B.A.T.M.A.N. advanced routing protocol has been included in the
+batctl: Linux kernel since 2.6.38, however the kernel module is only part of
+batctl: of the implementation. In order to create and configure mesh networks
+batctl: using the B.A.T.M.A.N. advanced protocol you need the batctl userland
+batctl: tool.
+batctl:
+batctl: Since B.A.T.M.A.N. advanced operates on layer 2 the common diagnosis
+batctl: tools do not work as expected. To solve this, batctl provides
+batctl: alternatives for ping, traceroute, and tcpdump.
e ogni volta mi ruba diverso tempo).
:cf