I used slackbuilds manually for many years. But it is impossible to manage manual updates So I went to sbopkg.
Just a silly question, does anyone use slackbuilds manually and how do they do it in the updates part?

I used to run SlackBuilds from SBo manually. Then I started using too many, so I switched to using sbopkg. Then I started maintaining a few SlackBuilds for SBo myself, so for testing I'll either run the SlackBuild manually or use sbopkg. Recently I've started using slackrepo (but I still use sbopkg on some packages because slackrepo has a little bit too much automation for me).

So currently - I rarely run a SlackBuild manually. The automation for sbopkg and slackrepo hit that sweet spot for me of automating mundane tasks, but still leaving me in enough control so I know what's going on.

Using sbopkg doesn't preclude you from still running a few SlackBuilds manually.

To answer your final question - how did I do the updates part (when running SlackBuilds manually): just run the SlackBuild and then use upgradepkg to upgrade to the newly built package. Kept a few older versions around in case I had problems with the new version. It gets to be a lot of work when you have more than just a few SBo packages (especially ones that get updated frequently).

(Further note: I just use pkgtools directly (installpkg, removepkg, upgradepkg) so I don't have to bother with pointing slackpkg or any other tool to my own repo of SBo packages. I find that works for me just fine.)

1 members found this post helpful.

Well I still use Slackbuilds myself…. This may not be the right way but I’m X I have Firefox open and a terminal. I select the package I want then click on each dependency working furthest back. I copy/paste links into terminal and build em via terminal.
Virt-manager took me with all dependencies 1.5/2 hours. But worked 0 issues.

I tried sbopkg but I couldn’t get a single thing to work. Going to create a VM and try some methods but every time I did it it acts like the package I want doesn’t exist.

3 members found this post helpful.

I use pre-compiled packages mostly from the Alien Bob repositories. It is a rare event when I need a program and cannot find it in Slackware or in a package repository like Alien's.

I mostly use sbopkg or alien bob's binaries. But I do have a dozen or so SlackBuilds from SBo and Alien Bob that I build manually because I made some customizations to the scripts.

To build SFS, I only use the SlackBuild of the entire slackware distribution: 1590 packages built from sources.

2 members found this post helpful.

Only way I ever use them!

Which inst a comment on sbopackage or anything of the sort just that I so often want to make a few changes to build options or build a chain without a particular dep or whatever that I prefer to just do it by hand.

2 members found this post helpful.

Yes, I use the SlackBuild scripts from SBo manually. Unless one is talking about things with ridiculously long dependency chains, like VLC or Xmonad, it's rather painless in my opinion.

1 members found this post helpful.

Arguably you're not running the SlackBuilds manually

The first POC in 2016 was built manually, look here : https://github.com/nobodino/slackwar.../memo-02022016

which is not the case now.

I also have:
204 *SBo packages
42 *ponce packages
built from sources

1 members found this post helpful.

I do, but I don't upgrade until something doesn't work. But I use about 40 packages from SBo on my box at work, and 11 packages on my i686 laptop, so it's not so many in the end.

Same here. Just a handful of actual slackbuilds compiling from source, mostly binary packages from other sources.

14.2 I use binaries converted using rpm2tgz for OpenOffice and Ruario's Firefox script to have a current Web browser. And some of Alien Bob's binary slackbuilds (VLC, Chromium...). A few slackbuilds like R, Octave and Lyx needed actual compiling. The most fiddly was Shotwell. And maxima/wxMaxima. Then there was CherryTree... perhaps I do need to look at automation when 15.0 beds in. Something like OpenBSD's pkg_add -u would be ace.

15.0RC Just done the R/RStudio from the 'unofficial' slackbuilds. RStudio slackbuild is a repackaging of the debian binaries. And Lyx (no extra dependencies and the new texlive package in base expands the potential e.g. tikz diagrams and all).

I do. I like the "ritual" of building from sources, checking/adapting slackbuilds, etc. But, as many others said, I don't have too much packages to upgrade.

1 members found this post helpful.

I tried and liked sbopkg and sbotools and a couple of others but eventually, I just found myself back to using slackbuilds by themselves. old habits die hard?

1 members found this post helpful.

I first learned how to manually use slackbuild scripts. These days I use sbopkg. I'm very grateful for the Slackers who maintain our repository.

2 members found this post helpful.