and an include folder, and some stuff in lib64, and so on. So that's all the components of, you know, all the source code has been compiled into whatever it got compiled into, which actually it looks like it's mostly, yeah, a single library, a dot so file, and then a bunch of header files put into include. And then, you know, again, there's documentation such as the specifications that come with the package, and a changelog, and the Slack description file, and so on. So there you go. That's the manual way of using a Slack build. And if you think that sounds like it could get tedious after, I don't know, 20 installs, then you're right, that can get tedious. That would be a very, that could be a very potentially slow way to get new software onto your Slackware system. Because remember, I started this looking for fdk-aac, and I haven't even installed that yet. That was just the dependency. That was libfdk-aac. So now I still have to go back to fdk-aac and download that source code and (18/54)
You are viewing a single comment's thread from: