LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-14-2016, 02:05 AM   #196
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,083

Rep: Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881

Quote:
Originally Posted by brobr View Post
I am all for pragmatics to make things work; principles are guides one might need to step away from when something different comes along..
You are not talking about principles then, what you describe is opportunism.

Anyway, the principle behind SlackBuilds.org is that it provides build scripts that create working packages. The core principle is that SBo aligns itself with the way SlackBuild scripts are written in Slackware itself. The scripts in Slackware do not download the source code for you, therefore a SBo script will not do that either.
Other people / other sites have different points of view and thus implement their SlackBuild scripts differently. For instance my own SlackBuild scripts perform an automatic download of the source if that is not present locally.
Thanks to the clearly defined principles behind SBo, other people were able to create the missing links in the chain of building a Slackware package. The sbopkg, sbotools, slackrepo tools will do the download for you and then start the SlackBuild script to compile a package for you. Quite convenient and in line with the principle "do one thing and do it right".
 
1 members found this post helpful.
Old 05-14-2016, 05:23 AM   #197
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
For SBo maintainers: downloads from github

tl;dr

if you put something like this in the .info file
Code:
DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz"
then the tarball name will be the same whether you use wget/curl with or without content disposition, or 'save as' in a browser, and therefore you won't need to deal with two possible tarball names in the SlackBuild.

long version

Over in the "requests for -current" thread, there was a brief discussion about downloads from github. Github dynamically creates downloads for the version requested in the URL, and the name of the dynamically created tar.gz (or zip) file is indicated via "content disposition". So if you use wget or curl without without content disposition, you generally get a filename that just has the version number, but if you use a browser, you get a different filename that has a more conventional name <package>-<version>.tar.gz. Our SlackBuilds generally have to deal with both filenames, with code something like this:

Code:
tar xvf $CWD/v$VERSION.tar.gz || tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
But! ppr:kut has worked out a much better solution! There are several different forms of github URLs for downloading, but this form is the most flexible:
Code:
https://github.com/username/repository/archive/version/filename.tar.gz
  • version is a git tag, or a git commit (commits can be abbreviated, but github will expand them to the full 40 character SHA1 commit id)
  • filename is anything you want -- it doesn't determine the version downloaded or the name of the top level directory inside the downloaded tarball (github just looks at the suffix to see if you want .tar.gz or .zip)

Therefore, if you specify filename as the expected content disposition name, wget/curl *without* content disposition will use the same name! For example: https://github.com/trizen/clyrics/ar...cs-0.04.tar.gz

Thanks ppr:kut!
 
4 members found this post helpful.
Old 05-14-2016, 01:17 PM   #198
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 653

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by Alien Bob View Post
You are not talking about principles then, what you describe is opportunism.
What do I personally gain by trying to add some stuff that bridges a gap? Is that 'opportunism'?? Is it necessary to put things in such a negative way when there is actually no other logic behind it but a particular philosophy or a constraint to keep thing workable in general? "NO ADDITIONS ALLOWED" . Fine; I understand now that such additions do not fit the SlackBuilds.org line of thought. But it still still would not make the script behave differently as intended, would it? Anyway, thanks for all your 'opportunistic' scripts (although I would call them 'pragmatic'), I love them, learn quite a bit of them but now I understand why they live a life of their own.....

Last edited by brobr; 05-14-2016 at 01:19 PM.
 
1 members found this post helpful.
Old 05-14-2016, 03:14 PM   #199
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 311

Rep: Reputation: 183Reputation: 183
Quote:
Originally Posted by brobr View Post
What do I personally gain by trying to add some stuff that bridges a gap? Is that 'opportunism'??
I think it is, as you don't want to see that there's no gap for the majority using SBo.
Quote:
Is it necessary to put things in such a negative way when there is actually no other logic behind it but a particular philosophy or a constraint to keep thing workable in general?
It seems you are annoyed because your suggestion wasn't welcomed. I understand this, it can be frustating to put time in a project without earning postive feedback. But i also think
that is was well explained why your suggestion doesn't fit in the buildscript, that's not negative.

Quote:
Oh, I see, did I stumble on a sectarian issue;
That is negative.

Quote:
But it still still would not make the script behave differently as intended, would it?
You will never find such a thing in a officially shipped SlackBuild. Your suggestion is overhead. Don't get me wrong, i personally build my packages with my own toolchain, which has not much in common with SBo. That doesn't stop me providing Slackbuilds that fit to SBo.

Franzen
 
1 members found this post helpful.
Old 05-15-2016, 05:31 AM   #200
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,083

Rep: Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881
Quote:
Originally Posted by brobr View Post
What do I personally gain by trying to add some stuff that bridges a gap? Is that 'opportunism'?? Is it necessary to put things in such a negative way when there is actually no other logic behind it but a particular philosophy or a constraint to keep thing workable in general? "NO ADDITIONS ALLOWED" . Fine; I understand now that such additions do not fit the SlackBuilds.org line of thought. But it still still would not make the script behave differently as intended, would it? Anyway, thanks for all your 'opportunistic' scripts (although I would call them 'pragmatic'), I love them, learn quite a bit of them but now I understand why they live a life of their own.....
Yes, "pragmatic" would perhaps have been a better word.
Still, the SBo project has a set of principles it adheres to, which has made it the ultimate and invaluable source of build scripts it is today.
You will only see a few build scripts of mine in SBo's repository and that is because my own build script philosophy does not fit in with the SBo philosophy. And that's just fine, because both have merits. There is no "my way or the highway" here.
The thing you should understand is that more people have wanted or tried to add functionality to SlackBuild scripts when submitting them for review by the SB0 admins. These have been and will be rejected. Please let the 3rd party tools surrounding the SBo project do what they do best, and leave the SlackBuild scripts on SBo do the core job of building the package.
Or setup your own package or script repository, it is not so difficult and more people are doing that.
 
Old 05-15-2016, 07:52 AM   #201
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 653

Rep: Reputation: 170Reputation: 170
@AlienBob
Quote:
Please let the 3rd party tools surrounding the SBo project do what they do best, and leave the SlackBuild scripts on SBo do the core job of building the package.
.
The mistake I made was to assume that sbopkg was part of SBo, instead of a 3rd party tool, plus the fact that that's the only one I use; this didn't help to keep the distinction between all of these tools in mind.

@franzen.
Quote:
there's no gap for the majority using SBo
This needs an insight into the user-base of the SBo-scripts plus a comparison to that of the 3rd-party tools; without a poll or idea how many are using what method to apply the SBo-scripts, all our additions to scripts can be called 'opportunistic'. I don not think that word is appropriate at all, as we're trying to solve problems/hitches one runs into; and there are several ways to solve these; the one I proposed is obviously not fitting SBo and that's fine; I will keep it to myself.
 
Old 05-15-2016, 08:02 AM   #202
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,083

Rep: Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881Reputation: 6881
Quote:
Originally Posted by brobr View Post
all our additions to scripts can be called 'opportunistic'.
Don't push my comment out of context. My remark about opportunism was about this statement of yours:
Quote:
... principles are guides one might need to step away from when something different comes along.
Either you have principles and then you stick to them, or else you are an opportunist who runs away with all the latest fads.
 
Old 05-15-2016, 10:59 AM   #203
jefeyay
LQ Newbie
 
Registered: Sep 2015
Posts: 20

Rep: Reputation: Disabled
thank you thank you thank you

After fighting with my new laptop for weeks, Ubuntu was the only distro where I could get Wifi and trackpad working. It was, however, unstable and randomly took forever to boot and shutdown so I decided to attempt with slackware-current. Haven't figured out the trackpad yet but this current SBO repo has made things so much easier. love you guys! and all the people making Slackware what it is. :-)
 
Old 05-15-2016, 12:17 PM   #204
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 653

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by Alien Bob View Post
Either you have principles and then you stick to them, or else you are an opportunist who runs away with all the latest fads.
Wow. Really? Ever thought of the possibility that it can be a bit more complicated than this? The use of the 'Either/Or' operator as a life-principle is a major cause of (self-inflicted) human trouble. I prefer the inclusive 'And/Or', that keeps room for fuzziness and helps to take care of exceptions that come along and do not need to be dismissed when they don't happen to completely fit the common pattern the guide-rule applies to. And did you not notice that that line of mine actually can be read as a concise version of this pragmatic principle, especially in the context of the discussion about the addition of an error-clause (for many a good programmatic principle)?

Last edited by brobr; 05-15-2016 at 12:19 PM.
 
Old 05-15-2016, 08:33 PM   #205
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware, OpenBSD, Linux From Scratch
Posts: 1,419

Rep: Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788Reputation: 788
SBo scripts not building on current (read 1st post, pls)

Maybe a new thread should be created to continue this discussion?
 
Old 05-16-2016, 04:21 PM   #206
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 540

Rep: Reputation: 258Reputation: 258Reputation: 258
Clementine 1.3.1 fails to build without some (unstated) hard dependencies. Besides protobuf (which is already stated in the SBo site), there are the following dependencies:

* cryptopp (and this should be done from the latest SlackBuild files from the repo since the darned software does not provide a pc file)
* libechonest (totally useless IMHO, and there's no compile switch to disable support)

Besides, unless you add -DENABLE_SPOTIFY_BLOB=OFF to the build parameters, a spotify blob would be mandatory.

I proposed these changes via GitHub.
 
Old 05-16-2016, 05:11 PM   #207
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,171

Rep: Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396
Quote:
Originally Posted by sombragris View Post
Clementine 1.3.1 fails to build without some (unstated) hard dependencies. Besides protobuf (which is already stated in the SBo site), there are the following dependencies:

* cryptopp (and this should be done from the latest SlackBuild files from the repo since the darned software does not provide a pc file)
* libechonest (totally useless IMHO, and there's no compile switch to disable support)

Besides, unless you add -DENABLE_SPOTIFY_BLOB=OFF to the build parameters, a spotify blob would be mandatory.

I proposed these changes via GitHub.
those changes are already applied in master branch long time ago

https://slackbuilds.org/cgit/slackbu...5e8deafaa44921

i don't see -DENABLE_SPOTIFY_BLOB=OFF in the SlackBuild and it still work without it
 
1 members found this post helpful.
Old 05-16-2016, 05:25 PM   #208
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 481Reputation: 481Reputation: 481Reputation: 481Reputation: 481
"soundtouch" would build but the source is no longer at the repo here www.surina.net. I sent an email last year to the maintainer. Oh well there is a newer tarball around. just google it you will find it point the script at it.
 
Old 05-16-2016, 05:48 PM   #209
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 540

Rep: Reputation: 258Reputation: 258Reputation: 258
Quote:
Originally Posted by willysr View Post
those changes are already applied in master branch long time ago

https://slackbuilds.org/cgit/slackbu...5e8deafaa44921

i don't see -DENABLE_SPOTIFY_BLOB=OFF in the SlackBuild and it still work without it
Oops. My bad.

Re: Spotify, it seemed that I thought this was due to an error message complaining of the lack of cryptopp.
 
Old 05-16-2016, 06:42 PM   #210
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,171

Rep: Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396
Quote:
Originally Posted by Drakeo View Post
"soundtouch" would build but the source is no longer at the repo here www.surina.net. I sent an email last year to the maintainer. Oh well there is a newer tarball around. just google it you will find it point the script at it.
Updated to 1.9.2 in my branch
 
  


Reply

Tags
current, sbo, sbopkg, slackrepo


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error building gst1-plugins-good 1.4.1 from SBO l0rddarkf0rce Slackware 4 10-06-2014 05:58 PM
[SOLVED] Failure building nvidia-kernel Slackbuild from SBo sysfce2 Slackware 7 07-02-2011 01:10 AM
problems building fontforge from SBo gtludwig Slackware 7 05-12-2010 01:52 PM
Pls help me take my 1st step! verysoon Fedora - Installation 2 12-12-2005 07:49 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:35 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration