slackbuilds.org. It's important to understand that, because very frequently, not very frequently, because if sbopkg fails to build a package or whatever, then you do need to debug sbopkg first. So you would want to, for instance, attempt a manual build of that package first, before reporting that something is broken on slackbuilds.org. Because from slackbuilds.org's angle, from their point of view, I should say from our point of view, slackbuilds.org has not, that script has not broken. It builds fine, as long as you do it correctly, manually, etc. sbopkg maybe has failed in some way, maybe there's a special requirement that it didn't account for, or that it can't account for, and so on. So there is that separation, and it's not just a separation of, well, it's technically not the same thing. It is a separation because, like, literally, sbopkg or any automated tool can introduce errors that don't technically exist in the slackbuild script. And I think that color-d example would be a (30/54)
You are viewing a single comment's thread from: