Very good story everyone! I made links + xterm to work with slackbuilds.org The issue that I had more difficulty / "laziness" was to keep viewing the changelog to update

Only when I want something updated outside of normal SBo updates. But there's no way I'd manually figure out the dependency tree for something like vlc (or pandoc ) and mess around with that, versus just "sboinstall vlc" (or whatever your favourite SBo helper's install command is).

The most time I create my own builds, as an example Xfce-4.16-nonCSD, LXqt, Elementary DE etc.

Yes I still build SBO packages manually. I have a lot of installs for various reasons so what SBOs I build vary a bit but a couple major ones are WINE-Staging (and winetricks), conky, hwinfo, isomaster, and dozens of support libs.

1 members found this post helpful.

I have always used SlackBuilds “manually”.

My SlackBuilds are on a Git repository on my machine, I build from there, then I install or upgrade the resulting package with upgradepkg.

I never felt the need for another method.

1 members found this post helpful.

I personally still use SlackBuilds from SBo manually. In part because I have a certain distrust of most automated or semi-automated tools (no matter how good they are) and in part because as I get older my need for complex applications is less.

1 members found this post helpful.

Other than slackpkg and slackpkg+, everything is fairly manual. I tend to customize a bit here and there (configure options, etc). I keep a local binary repo via slacpkg+ to remove/install/reinstall as needed. I don't really upgrade packages every time a new source appears, and try to avoid repeatedly downloading stuff (local HD mirrors, old modem dial-up habits die hard). As long as the software works, I use it until I run into a bug, security issue, or it fails to run due to a core package update.

Yes I still build manually, although I have written a couple of scripts to prepare a build by generating dependency lists, fetch the sources and check md5sums, etc.

Like some others, I also keep a local source and package repo of all that I build (along with a "built-as" file, a generated list of versions of all dependencies and notable options used at build time).

Due to hardware problems in the past year that level of organization has slipped a bit behind but I intend to get it back on track with 15.

I admit I have never looked at sbopkg but may do so as I reboot!

I started out building everything manually, then I decided that was too tedious and started to script it (for fun/learning, as there were existing tools available of course), and then I decided to create a user interface on it, inspired by Midnight Commander. Thus, sboui was born.

Manually. But I prefer a minimalist approach to my computing experience so I avoid programs with a large number of dependencies. I also run -current which includes several of the boilerplate dependency trees so there are a *LOT* of slackbuild scripts I no longer need to think about.

I only do SlackBuilds manually when I'm maintaining mine, or upgrading a version before appears in sbopkg, or if won't run in sbopkg (Java) or if I don't want to replace what I have (ZFS, before trying new kernel,) etc.

I only build manually, preferably from source.
I first test my scripts as an ordinary user, then
create the package as root.
Also, everything should be done offline.
If any Makefile have entries for downloading stuff,
I first download the required files prior to building, and modify
the Makefile accordingly.

2 members found this post helpful.

Not impossible. I create my own SlackBuild scripts for all my third party packages. The exceptions are multilib packages and 11 packages from Alien Bob, both repositories are mirrored locally for local access across my LAN. The only package I download via the internet is slackpkg+. When a rebuild or upgrade is needed I manually edit the script and run it to create the package. The resulting package is then placed in my personal repository for use on all my systems by slackpkg with slackpkg+. I have 143 packages I handle manually. I use the script header to document the dependencies, both the build/runtime requirements for that package and what package(s) needs that package. So if I open the SlackBuild script for package A, I see the packages B, C, D are needed to build packages A, in that order. I also see that packages A is needed to build package E and F.

My SlackBuilds do thing that cannot be done with SBo.

Yes, a lot!

1 members found this post helpful.

I rarely use slackpackages but then always run them manually, often editing as I go.