use cases for all those things. Either way, you can get the repository onto your computer, and the way that you do that is you either do an Rsync command or a Git command or whatever. The path to the repository is slackbuilds.org slash repository slash 15.0, or whatever the release of your Slackware system is. You can find the release number of your Slackware system by doing a cat on slash etsy slash os dash release. Version string is set to something, or the version ID. Those really ought to be the same, I think, almost always. It's 15.0 in this case. A month ago it was 14.2, and some other time in the future it'll be 15.1 or 16.0 or whatever, but that's the release number. So as long as Slack Builds is up to date, then it'll have that repository number available to you over protocols including Rsync, Git, HTTP, and so on. So I'm going to do that, I guess. And I say I guess because I don't actually do it this way, but I'm going to go into how I do normally do it later, very soon. So (22/54)
You are viewing a single comment's thread from: