I don't have an account on GitHub, but I'll set one up, with a contact E-Mail address I'll use on all my projects. I would have had to use it eventually, as I've got projects piling up just itching to be shared. lol
You can find what I've called roks (I've mentioned what prompted me to write it
) here:
https://github.com/terminalforlife/roks
I'm completely new to GitHub (at least as far as having an account), so if I've done something silly, please let me know!
Moments later...
I forgot to address your questions. I guess I was more thinking of roks as I intend it to be viable on more than just Mint. I'm a big fan of dep checking and using as few non-essentials as possible. If you can do it with a builtin, it has a chance to be faster, and it's more portable. This has at least been my experience and what I've learned from others. As for linux-image-extras, I'm looking into that now, but I'm pretty sure it would be best to specify all, or at least provide the option to. I'm a big fan of options too; giving the user the power to do what they want; I always love that in a program.
By the way, I forgot last night that apt in Mint is different to apt in other places, so, since apparently apt in Mint is a python wrapper for apt-get, apt-cache, etc, that would mean my using apt-get by default isn't necessarily the better move, at least in Mint, but I can't see it being harmful.
I forked it, thinking it with something else, but I totally did the wrong thing. I hate GitHub >.< but I'm sure I'll figure it all out eventually. I have no idea how to suggest changes to what you have. I thought committing was posting a change, which can then be revised and possibly put forward by the person(s) behind the repository. Sorry if I caused any confusion.
Oh, oh, and and (lol) I believe you're right about awk being part of Mint by default; I've yet to see a Mint setup without it, but then the user can just remove it, or have some other sort of custom setup; this is why I don't like to assume too often.