> Is [#! taking a relative interpreter path] intentional?
> What's more, the relative interpreter filename is taken relative to
> the current directory, not relative to the script directory.
That's exactly what I'd expect, and what I'd say should happen: it's
consistent with ~every other use of r
On Sun, 14 Aug 2022 at 03:13, Robert Elz wrote:
>
> The normal default path for sh comes from sysctl user.cs_path
> and if there was a desire to alter that, that would be the place to
> do it (as in, by setting that in /etc/sysctl.conf).
This seems like a critical fulcrum we already have. If so,
On Wed, Aug 17, 2022 at 08:29:48AM -0400, Mouse wrote:
> > Is [#! taking a relative interpreter path] intentional?
>
> > What's more, the relative interpreter filename is taken relative to
> > the current directory, not relative to the script directory.
>
> That's exactly what I'd expect, a
On Mon, Aug 15, 2022 at 10:50:39AM +0200, Hauke Fath wrote:
> > Argument 2:
> > the stuff in base is canonical and it's wrong for random whatnot to
> > arbitrarily override it. I admit I don't fully understand argument 2 [...]
>
> To give an arbitrary example: I had ${PREFIX}/{s,}bin first in
On Mon, Aug 15, 2022 at 04:36:13PM +0700, Robert Elz wrote:
> Date:Sun, 14 Aug 2022 21:41:08 +
> From:David Holland
> Message-ID:
>
> | There's another wrinkle, which is that /usr/local and /usr/pkg should
> | come before /usr... except that this point
On Tue, Aug 16, 2022 at 02:03:49AM +0700, Robert Elz wrote:
> So, for example if the shell were to not start with line editing
> enabled (to borrow from one of the recent issues) a moron user
> with complain about how useless it is, and moan a lot, and that's
> about it. A user who is merely
On Tue, Aug 16, 2022 at 08:59:13AM +0200, tlaro...@polynum.com wrote:
> But the argument "if something is modified, that"s the problem of the
> user" can be reversed: NetBSD provides utilities whose
> functionnalities it relies upon. So, by default, the system should use
> its utilities, the on
