Dropbox public folder alternative for SBo sources?

bassmadrigal · 03-23-2017, 07:05 AM

Quote:

Originally Posted by 55020

It's possible to craft a Github download for a specific release as a variant of the trick Chris Willing outlined above. I'm not saying you should do that, it's not pretty, but it's possible.

The URL would be

Code:

https://github.com/cwilling/hoorex/archive/101df8676c46d9c6c55206a5f627359b1e8f7877/hoorex-101df8676c46d9c6c55206a5f627359b1e8f7877.tar.gz

But that needs quite a lot of extra code in the SlackBuild, and the 40 character git commit is really ugly. You can shorten the first one in the url, but it has to be the full 40 chars in the tarball name and in the tar extract and the top level directory name. If you are thinking "noooooo!" then that's ok, your selfhosted snapshots are perfectly acceptable.

To further 55020's post, here's an example of a SlackBuild that uses commit tarballs (although, this has multiple downloads, so it is a bit more convoluted than a single download would be). You can check out the parent directory to see the glPortal.info file.

https://github.com/bassmadrigal/slac...tal.SlackBuild

I use the first seven characters of the commit for the version number and then use SRCVER to contain the full commit ID. Then you just need to update the extraction section to replace VERSION with SRCVER.

Code:

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$SRCVER
tar xvf $CWD/$PRGNAM-$SRCVER.tar.gz
cd $PRGNAM-$SRCVER

chris.willing · 03-23-2017, 06:29 PM

Although the OP's original problem seems to be solved, I was nevertheless curious about how to host externally generated tarballs at github (rather than github tarballs generated from github hosted source code). There may be other ways but I figured out a pretty simple method described here.

The target tarball is unittest-cpp-2.0.0.tar.gz which I just happened to have lying around in /tmp for some reason that I don't recall right now. In the local copy of my hoorex project, I made a new branch "testbinary" from which I cleaned out all files and then copied and git added the unittest-cpp-2.0.0.tar.gz file. Of course if you made a dedicated project to do this, you'd just use the master branch. After committing the changes, I pushed the new branch back to github. The direct download by wget of the new external tarball is:

Code:

wget https://github.com/cwilling/hoorex/raw/testbinary/unittest-cpp-2.0.0.tar.gz

i.e. construct the url by first pointing to your project (hoorex, in this case), add "raw" directory, add the branch name directory (testbinary, in this case) and finally add the name of the tarball you previously pushed.

chris