I thought about organizing directory structure and put together a simple script intended to make uploading to this repo pain-free.
Here's how I see directory structure:
/Vector-SlackBuilds
VL7
data - upload-0.1 puts all files here
archives - all files from data compressed into a single tarball
old - old versions kept here just in case
tools - various useful scripts(upload-0.1 is here)
trash - things that are no longer(were never) useful, but might help in the future
upload - things to be uploaded go here
And here's the script:
#!/bin/bash
# upload-0.1 script by budulay
# Archives and uploads package data from the upload directory to SlackBuild repository.
# Intended to be run from Vector-SlackBuilds/tools directory
# You are free to use, change and distrubute this to your liking, but I make no guarantees
# that it will work as intended or at all and that it will not harm your system.
# So if suddenly earth starts shaking, or nukes show up on the horizon, you have been warned.
#Accept command line input
PACKAGES=("$@")
#Establish "root" directory
cd ..
RT=$PWD
#For every argument from command line:
for NAME in ${PACKAGES[@]}
do
cd $RT/uploads
#Check if a directory specified from command line exist
if [ -d $NAME ]
then
#If there is already a package in archives, move it to old and remove from data
#TODO: use git to upload old to repository
if [ -f $RT/VL7/archives/$NAME.tar.gz ]
then
mv $RT/VL7/archives/$NAME.tar.gz $RT/VL7/old/$NAME-old.tar.gz
rm -R $RT/VL7/data/$NAME
fi
#Compress package into tarball, move it to archives; move package to data
tar -cvf - $NAME | gzip -c > $NAME.tar.gz
mv $NAME $RT/VL7/data
mv $NAME.tar.gz $RT/VL7/archives
cd $RT
#Add package to git's list of tracked files
git add VL7/data/$NAME/* VL7/archives/$NAME.tar.gz
#Add package name to the commit message
MESSAGE=$MESSAGE" "$NAME
else
echo "No directory $NAME in uploads..."
fi
done
#commit
git commit -m "$MESSAGE"
#upload
git push origin master
I can also be found
here.
What it does:
When run from the tools directory, it takes as command line arguments names of packages.
Then it goes into the upload folder and looks for directories with the names specified above.
It compresses all the ones it finds into tarballs and moves directories to VL7/data and tarballs to VL7/archives.
Then it uploads it all to the repository.
Usage example:
Put upload-0.1 into ~/Vector-SlackBuild/tools
Create directory ~/Vector-SlackBuild/upload/wine
Put SlackBuild, slack-required and other files into that directory
Run upload-0.1 from the tools directory, specifying wine as an argument:
./upload-0.1 wine
So for someone to start using this, they'd need to create a github account, clone the repository(or manually create the file structure that I described), send me your account name so I can give you write privileges on the repository and start using it
I can put together more detailed instructions if anyone needs them.
@Joe1962
That would be a handy tool to have.
