[SOLVED] sqg and existing packages

rootaccess · 01-02-2024, 01:55 PM

I'm attempting to build obs-studio and already have vlc

Code:

sqg -p obs-studio

produces quite a bit of dependencies but I already have vlc installed. Would this rebuild vlc or is there some way it checks /var/log/packages to know if its already installed or not?

Windu · 01-02-2024, 02:09 PM

The sqg script merely generates the queue files but does not compile anything. For that you would then use "sbopkg -i -k obs-studio" where the "-k" options tells sbopkg to skip the already installed packages.

rootaccess · 01-02-2024, 03:28 PM

Quote:

Originally Posted by Windu

The sqg script merely generates the queue files but does not compile anything. For that you would then use "sbopkg -i -k obs-studio" where the "-k" options tells sbopkg to skip the already installed packages.

Yes I actually generate a queue with -o and load that into sbopkg but totally forgot about using sbopkg on the command line. Thanks for referencing the -k flag to skip.

rootaccess · 01-02-2024, 08:07 PM

Just wanted to report back and mention that the -k must not precede the queue name. The queue name must proceed -i so I put -k at the very end.

willysr · 01-02-2024, 08:45 PM

yeah, you should use -k -i obs-studio instead

rootaccess · 01-02-2024, 09:16 PM

im building obs-studio on another slackware 15 i got laying around right now because i did my other one sort of manually first. it is currently building quite nicely. just wanted to say this method is a charm. this totally beats out any system i know. you cant do this stuff on debian or redhat systems. to be able to build from source and the fact that slackbuilds have been developed specifically to compile from source onto slackware is something no other system has besides BSD and arch, i believe.

i actually did not generate an output file with -o from sqg but i thought that would work. so instead, i ended up simply doing

Code:

sqg -p obs-studio
ls -t /tmp/sqg > obs-studio
sbopkg -i obs-studio -k

yes its slower to compile from source where there are packages available for deb and rpm but sometimes we want to compile from source to modify stuff or just to be sure no one d**ked with the application that we want to use (some of us do read the source code looking for anything nefarious!). another great thing about slackware is

Code:

rpm2tgz

i've done this for google-chrome. it's great to have many options to get our packages. thank you slackware team.

Daedra · 01-02-2024, 09:21 PM

Quote:

Originally Posted by rootaccess

im building obs-studio on another slackware 15 i got laying around right now because i did my other one sort of manually first. it is currently building quite nicely. just wanted to say this method is a charm. this totally beats out any system i know. you cant do this stuff on debian or redhat systems. to be able to build from source and the fact that slackbuilds have been developed specifically to compile from source onto slackware is something no other system has besides BSD and arch, i believe.

i actually did not generate an output file with -o from sqg but i thought that would work. so instead, i ended up simply doing

Code:

sqg -p obs-studio
ls -t /tmp/sqg > obs-studio
sbopkg -i obs-studio -k

yes its slower to compile from source where there are packages available for deb and rpm but sometimes we want to compile from source to modify stuff or just to be sure no one d**ked with the application that we want to use (some of us do read the source code looking for anything nefarious!). another great thing about slackware is

Code:

rpm2tgz

i've done this for google-chrome. it's great to have many options to get our packages. thank you slackware team.

Just in case you don't know, you can speed up your compile by using all your CPU cores. To do this in sbopkg, edit /etc/sbopkg/sbopkg.conf and add the line in red

Code:

DIFF=${DIFF:-diff}
DIFFOPTS=${DIFFOPTS:--u}
RSYNCFLAGS="${RSYNCFLAGS:---verbose --timeout=30}"
WGETFLAGS="${WGETFLAGS:--c --progress=bar:force --timeout=30 --tries=5}"
export MAKEFLAGS="j?"

with ? being the number of CPU cores you have plus one. so on my system its j25.

rootaccess · 01-02-2024, 09:28 PM

Quote:

Originally Posted by Daedra

Just in case you don't know, you can speed up your compile by using all your CPU cores. To do this in sbopkg, edit /etc/sbopkg/sbopkg.conf and add the line in red

Code:

DIFF=${DIFF:-diff}
DIFFOPTS=${DIFFOPTS:--u}
RSYNCFLAGS="${RSYNCFLAGS:---verbose --timeout=30}"
WGETFLAGS="${WGETFLAGS:--c --progress=bar:force --timeout=30 --tries=5}"
export MAKEFLAGS="j?"

with ? being the number of CPU cores you have plus one. so on my system its j25.

thanks. i had wondered why it is so much slower on this machine. its an i5 M560 and my desktop is an i7 8700k but i will definitely make these changes.