2 ms·
Requiring git, vim, and bash to pull in a fork of their software instead of the vanilla version when the packages already exist as OpenBSD packages doesn't soun
by qbrass 3y ago
Requiring git, vim, and bash to pull in a fork of their software instead of the vanilla version when the packages already exist as OpenBSD packages doesn't sound like the Suckless philosophy.
And apparently nobody's used this thing anyway, including the person who made it, because the scripts have an obvious bug in them that won't let them run on OpenBSD.
That's after this thing has been posted on here at least 3 times to my knowledge.
- bradley_taunt 3y agoAuthor here - it is true that you could avoid the need for vim or bash (I just personally enjoy having those in my toolset) As for this: > And apparently nobody's used this thing anyway, including the person who made it, because the scripts have an obvious bug in them that won't let them run on OpenBSD I've used this installer on multiple machines (x260, x201, M73 Tiny) and am writing this comment on my X201 running OpenBSD via this installer _right now_. Could you elaborate on the bug(s) / even open a patch is that is the case? Thanks!
- the-printer 3y agoYour repo was my first time trying to find a bug in any kind of code other than my own. So bear with me, please. The only thing I think may cause an issue is that `bash` should be installed in `/usr/local/bin` on OpenBSD and not `/bin/bash` if the installation is done through `pkg_add`. I know I've had to make that change when copying shell scripts written on Mac over to an OpenBSD machine. Your mileage may be varying.
- bradley_taunt 3y agoOh interesting! I’m going to have to look into that for sure. Thank you for the heads up, I didn’t know about this. Much appreciated!
- deleted 3y ago[deleted]