[SOLVED] Is https://slackware.nl/people/alien/slackbuilds/rosegarden/build/ for both current and stable ?

fredmyra · 05-29-2022, 06:34 PM

I did install rosegarden under Slackware-current back in June last year, immediately after Bob Alien added it to his repository, but I don't remember how I did it. (It is still working fine in that system)

Now I want to install it in Slackware64-15.0 and I am not sure if the folder at https://slackware.nl/people/alien/sl...egarden/build/ is the right one for this.

I am not well acquainted enough with Slackware to reach any conclusion on this on my own.

I found rosegarden on sb0, but the source is from sourceforge and I kind of prefer having the Bob Alien's package.

0XBF · 05-29-2022, 09:24 PM

The link you posted is to AlienBob's slackbuild script, which could be run on either current or 15.0, as long as you build out the dependencies first.

If you just want to install the binary package, then you are in the wrong directory (you are in .../build/). Go back up to this directory: https://slackware.nl/people/alien/sl...ds/rosegarden/

Then from there you can go down to 'pkg' for 32 bit, or 'pkg64' for 64 bit. Then below that you will find binary packages for both 'current' and '15.0'. For example, here is rosegarden for x86_64, on slackware 15.0: https://slackware.nl/people/alien/sl...en/pkg64/15.0/

Please note the .dep file; you will have to install all those, and any deps they might have too. Alien should have all the deps needed for any packages he supplies.

fredmyra · 05-31-2022, 12:50 PM

Quote:

OXBF wrote:
The link you posted is to AlienBob's slackbuild script, which could be run on either current or 15.0, as long as you build out the dependencies first.

Thanks OXBF !

That was exactly what I needed to know. I did run it for current (in the current installation) but I did not know whether it could also be used for a stable istallation. I will read a little more on sbopkg ans sbotools, before I proceed. It was quite a bit of work when I did the dependencies manually.

By the way can you tell me what is difference between
https://slackware.nl/people/alien/slackbuilds/
and
https://slackware.nl/people/alien/sbrepos?

It seems to me that they have different structures but basically the same content - except perhaps for the "armv7hl" folder in sbrepos.

If that is true do you know what is the motivation?

0XBF · 06-01-2022, 08:01 AM

Your best option for official information on alienBob's public repos is probably asking him yourself on his blog: https://alien.slackbook.org/blog/

However, I will talk a little on how I use those repos.

The .../slackbuilds/ directory has everything in it, organized on a "per-package" basis. E.g. Under rosegarden you find the source files for the build, as well as binary packages for 32 and 64 bit systems. Organizing that way is convenient for a person to look around at the builds and run things manually.

The .../sbrepos/ directory only contains binary packages, and they are now all grouped by slackware version, and then arch in the next subdirectory. This is more convenient for using with a package manager, with the intended target being slackpkg+. For example, if you install slackpkg+ on a 64bit slackware-15.0, then you could configure to install packages in /etc/slackpkg/slackpkgplus.conf using a line like:

Code:

MIRRORPLUS['alienbob']=http://bear.alienbase.nl/mirrors/people/alien/sbrepos/15.0/x86_64/

You can't do that from the .../slackbuilds/ directory, since it isnt organized like sbrepos.

----------------------------------------------

As a side note: The slackpkg+ configuration makes it much easier to install packages from the alien repo, particularly the DAW software he provides, which have a number of dependencies. If you configure slackpkg+ to use his repo like that, then you can use a template file to install a number of packages in one command. I do this for *all* his DAW packages, using the template he provides here: https://us.slackware.nl/people/alien/tools/templates/

After slackpkg+ is installed, and daw.template is copied to /etc/slackpkg/templates/, then I install all the DAW packages by running:

Code:

slackpkg install-template daw

You could do something similar to just install rosegarden, though there are no premade template lists for that.

fredmyra · 06-06-2022, 09:47 AM

Quote:

0XBF wrote:
You could do something similar to just install rosegarden, though there are no premade template lists for that.

I looked at http://www.slackware.com/~alien/tool...s/daw.template and found it quite similar in appearance to a queue in SBo - but I am wary of my own interpretations when it comes to Slackware.

And then there was also a http://www.slackware.com/~alien/tool...w.template.asc so I wonder if I have to sign a template I make for my own use - that would probably be more difficult than making the template.

If a list of names of dependencies, one per line in a text file is sufficient, then I think I could go through the repo in question (alien's) and check the dependencies for a program I want to install, at all levels, and list then in a proper order. That sounds almost too good to be true if it would do the same job as a sbopkg queue. I wonder if this is absurd !

Windu · 06-06-2022, 10:12 AM

Quote:

Originally Posted by fredmyra

I looked at http://www.slackware.com/~alien/tool...s/daw.template and found it quite similar in appearance to a queue in SBo - but I am wary of my own interpretations when it comes to Slackware.

And then there was also a http://www.slackware.com/~alien/tool...w.template.asc so I wonder if I have to sign a template I make for my own use - that would probably be more difficult than making the template.

If a list of names of dependencies, one per line in a text file is sufficient, then I think I could go through the repo in question (alien's) and check the dependencies for a program I want to install, at all levels, and list then in a proper order. That sounds almost too good to be true if it would do the same job as a sbopkg queue. I wonder if this is absurd !

A template such as above is for using with slackpkg. This kind of template is nothing more than a list of packages which you request slackpkg to install, it's more convenient than typing the names of all the packages. Looking at that daw.template it looks like Alien Bob added a lot of the packages (probably all of them) which he puts in his DAW ISO, a Slackware Live system for musicians.
The SBo queues are something for sbopkg, not particularly affiliated with SlackBuilds.org themselves. Part of sbopkg is sqg, a SlackBuild queue generator" which is a script that parses all the .info files on SlackBuilds.org to find dependencies of packages and then dumps that information in queue files. Using a queue file, you get an automated way of compiling a package from source, starting with all its dependencies.

GPG-signing a template file is not necessary. I assume Alien Bob signs his file so that he can distribute both files and allow downloaders to verify that they retrieved the original unmodified file.

fredmyra · 06-06-2022, 11:13 AM

This is quite confusing to me but at least I am beginning to get used to it. I used sbopkg for installing Rosegarden, vlc, Qsynth and OBS-studio as a first experience. I still haven´t run the programs but I have already got their launchers on one of my desktop panels.

I don´t remember editing the /etc/slackpkg/slackpkgplus.conf, although I did read it a couple times. I had no memory of what is in it, as I have read so much these last few days - so I got a suspicion that perhaps I ended up installing from SBo's repo.

But I did some "slackpkg searches" and looked into /var/log/packages and I am sure that at least Rosegarden and vlc are alien's packages. Looking at /etc/slackpkg/slackpkgplus.conf now, I see that

Code:

PKGS_PRIORITY=(alienbob  restricted )
REPOPLUS=( slackpkgplus restricted alienbob )
# Slackware 15.0 - x86_64
#MIRRORPLUS['multilib']=https://slackware.nl/people/alien/multilib/15.0/
MIRRORPLUS['alienbob']=https://slackware.nl/people/alien/sbrepos/15.0/x86_64
MIRRORPLUS['restricted']=https://slackware.nl/people/alien/restricted_sbrepos/15.0/x86_64

So it seems to make sense now. But I am still curious about making templates. I remember having read some short passage about it, but today google did not come up with anything interesting - guess I will have to search a little harder when I have time. Right now I want to install a few more programs and then start testing them.

0XBF · 06-07-2022, 08:13 PM

It looks like you have slackpkgplus set up properly, except I have trailing '/' on each url. I'm not sure if it matters.

Once you have slackpkgplus set up to use the 'alienbob' repo, you can install any of those packages directly. He compiles them and provides the packages, so all you do is install rosegarden and all of its dependencies using slackpkg. For example:

Code:

slackpkg install rosegarden

Will install the pre-built rosegarden package from the alienbob repo. Then you do the same with the rest of rosegardens dependencies.

Another example:

Code:

slackpkg install alienbob

This will give you a list of ALL of the packages in the 'alienbob' repo, then you could deselect what you dont want and install the rest (probably a lot of packages to sort through, but a good test to see if slackpkgplus is set up properly).

NOTE: These examples only work if you DONT have alien packages blacklisted in '/etc/slackpkg/blacklist'.

That daw "template" I mentioned last time is just a list that you can feed to slackpkg, which then downloads and installs all the music/daw packages in the alienbob repo using slackpkg. Windu was explaining that in their post.

All these examples are using slackpkg, which is used to install pre-built slackware packages (i.e. packages in the *.tgz or *.txz format).

'sbopkg' its its own tool, and its used to compile and build packages from SlackBuild scripts using the slackbuilds.org repo. The key difference being the compiling from source stage, which takes longer. It can still build queues, it just compiles each package in order.

'slackpkg' is not building from source, only installing already built packages that someone else compiled.

I hope that all makes sense. I know you probably just want to install the software and be using it, but its good to know the difference.

fredmyra · 06-08-2022, 03:34 PM

Thanks OXBE !

Very useful and clearly presented info. Really appreciated.

I am trying to compile my packages as a way of gaining experience.

I am pretty sure that I compiled my packages through sbopkg using queues. I first wrote an ordered list of deps, with info from Sbo's site and them let sqg make its own list and compared it to mine before processing it through sbopkg.

But the packages appear in my system as alien's. I will try to be 100% sure about this if possible or I will try with some new package, and report back. But it may take some time, as right now I have a problem with some friend's machine running an obnoxious OS I won't even mention by name.

Marking this as solved.