On Sun, 24 May 2015, B Watson wrote:
> tar xvf $PRGNAM-$VERSION.tar.gz || tar xvf v$VERSION.tar.gz
I still whish Github wouldn't do this, but this workaround is perfectly
acceptable. Thanks for the hint!
--
___
SlackBuilds-users mailing list
SlackBui
Am 25.05.2015 16:52 schrieb Ryan P.C. McQuen:
I use:
if [ -e $CWD/$VERSION.tar.gz ]; then
tar xvf $CWD/$VERSION.tar.gz
else
tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
fi
So that a 'no such file or directory' warning won't get displayed.
Yeah, that's exactly what I've been doing in my scripts as
>tar xvf $PRGNAM-$VERSION.tar.gz || tar xvf v$VERSION.tar.gz
I use:
if [ -e $CWD/$VERSION.tar.gz ]; then
tar xvf $CWD/$VERSION.tar.gz
else
tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
fi
So that a 'no such file or directory' warning won't get displayed.
---
On Mon, May 25, 2015, 1:43 AM Heinz Wies
On Monday 25 May 2015 03:49:16 Thomas Morper wrote:
> Hello there,
>
> A user of one of my SlackBuilds discovered an interesting problem:
>
> If you follow the download link from the info file, pointing to a release
> on Github, you'll end up with different filenames depending on whether you
> us
On 5/24/15, Thomas Morper wrote:
> What would be a good way to handle this? Editing the SlackBuild script to
> handle both names doesn't seem very desirable.
tar xvf $PRGNAM-$VERSION.tar.gz || tar xvf v$VERSION.tar.gz
Desirable or not, a lot of builds do this now.
The only "broken build" prob
Hello there,
A user of one of my SlackBuilds discovered an interesting problem:
If you follow the download link from the info file, pointing to a release
on Github, you'll end up with different filenames depending on whether you
use a browser or a tool like 'wget', thanks to a 'Content-Disposit
