it'll install the thing that you need. Now, I'll admit, I do not tend to use that feature myself, at least not without rigorous investigation first. And I do that, or I don't do that, because I just want to know what my options are before just saying to install a thing and everything underneath it. That, to me, is not leveraging the advantage of Slack Builds all that well. And so I would prefer to find out what my optional dependencies are, maybe install them, maybe install them with yet extra options turned on on those, and then I continue from there. So the dependency resolution is an option, but it's more of an easy way to build a Q file than it is, I think, a way to actually install packages. And this, again, is a feature of Slack Builds for me. This is the flexibility of Slack Builds, and it's not something that I'm willing, or I think any Slack Build user is willing, to give up. The idea that the repository has just sort of a baked-in set of recommended installation features, and (41/54)
You are viewing a single comment's thread from: