Hello.

I'm pretty new to Slackware as well as to building packages from source (even with support of automation tools). I wonder how should i deal with third-party repos like slackbuilds repo of Ponce or AlienBob to keep my system clean and robust. Is it enough to use slackpg+ and sbopkg to install packages? Or i need some extra steps besides reading changelog? I've already installed multilib and wine from AlienBob repo and some packages from Ponce repo. The process is quite simple but not clear in depth for me, That's why i'm not certain was it installed as it should be or were there any (hidden) problems i should pay attention to. What should i do to prevent becoming my system a trash?

The second question is what's the simplest solution to share packages i've already build and installed. Let's say i have two separated systems (both current) and i'd like to share every installed package between them. Is it enough to copy .t?z archive from a system where i built a package to the second system and install it if any dependencies are satisfied?

I can't speak for Ponce, as I'm not familiar with his repo. However, you can be quite confident while using AlienBob's repos or Robbie Workman's.

It depends on your needs. Personally, I rarely ever have to compile from source on my Slack. SlackBuilds or other repos mentioned here, usually supply me with all I need for my systems.

I do occasionally install binaries in /opt. For example: Pale Moon browser, Calibre ebook library, etc.

First rule of any Linux is try to stay away from using anything outside of your distribution's main repository to avoid bad things. However, with Slackware, slackbuilds.org, AlienBob's repos, Robbie Workman's repos... and some others out there, are usually safe to utilize.

This usually works fine for me when transferring packages between my systems. However, they are all running the same versions of Slack and are set up very similarly.

---

Welcome to Slackware! I hope you find it to be as wonderful as I have over the last 14 years.

1 members found this post helpful.

Hi exfx and welcome to slackware.
I'm probably not the best advisor in your case, since I belong to the minority(?) of slackware users who rely on gslapt/slaptget for upgrading.

slackpkg, with the extension slackpkg+, should do the job. But since you want to follow upgrades in 3rd party repos and have gone multilib I advise you to carefully read AlienBob's exhaustive slackpkg+ documentation here:
https://alien.slackbook.org/blog/int...-repositories/

Also, read his multilib documentation: https://wiki.alienbase.nl/doku.php?i...kware:multilib

Remember that new packages (dependencies) are sometimes added to the slackware -current repo (or, of course, to 3rd party repos). You'll catch them by running "slackpkg install-new"

When on -current it's always a good idea to check the changelog. Look out for added packages and upgrades that affect other packages (e.g.the recent python3-3.8 upgrade)- those may affect 3rd party programs that will need rebuilding. Also look out for the line "Shared library .so-version bump." which may affect 3rd party packages - especially icu4c and boost. AlienBob's icu4c-compat and boost-compat packages are indispensable safeguards against package breakdowns.

It might also be a good idea checking this forum before upgrading, seeing if other users have run into problems with a recent upgrade.

If an upgrade creates problems, downgrading might be an option. Older packages can be found here:
http://slackware.uk/cumulative/ but use this option with care or you might be in a deeper hole than before

As to your second question: if you've downloaded or built a .tgz or .txz package and it works OK, it should be fine transferring it to another computer with identical setup and install it there, using "installpkg [packagename].txz

If you manually download a .tgz or.txz package from a trusted and reliable source - the official slackware repo, AlienBob, Ponce - you can be sure that it installs correctly and in its proper places.

2 members found this post helpful.

@vtel57, @kgha, thanks a lot for clarification. I try to go hand in hand with documentation and community trusted repos. Anyway practice accompanied by mistakes. Hope i will not bother community much with questions

As for caution while upgrading packages, i found information about how to make copies of old packages that are supposed to be upgraded, but forget where i found it...

Never a bother. Jeremy's LQ.org is here to help. I'm not always very active here, but I've been here for a while. I've found MANY answers to my questions here over those years.

Ponce is a trustworthy member and his repo is NO problem!!! I use some of his packages.

1 members found this post helpful.

also, ponce adapts SBo for -current

i use slackpkg+ for slackware packages and multilib and use sbotools with ponces "current" sbo repo
sbotools has the benefit over sbopkg of handling dependancies for you

I still have to try sbotools but sqg, shipped in sbokg, does that.

1 members found this post helpful.