somewhere else would be gigabytes and gigabytes. So that's a nice little bonus. But because you have the recipe, you can modify the recipe before you run it in ways that you can't really do with a binary package. With binary packages, your option usually is, well, you take what you can get, or you don't use the binary package, you go to the source of the binary package, and you rebuild a new binary package for yourself, which is perfectly, I mean, that's a fine way to manage a repository as well, but SlackBuild doesn't do that. It just doesn't offer the binary packages in the first place. It offers just the recipe. SlackBuilds.org, as the name implies, is a website. It has a web interface. You can go there, you can look around. I don't think that most SlackBuilds users actually use the website all that much. It's more of a reference point and just kind of a home for the repository. I think generally, the usual workflow is you go to SlackBuilds.org maybe once to download the recipes, (8/54)
You are viewing a single comment's thread from: