Re: nosh version 1.33

From: Jonathan de Boyne Pollard <j.deboynepollard-newsgroups_at_ntlworld.com>
Date: Tue, 18 Apr 2017 17:01:56 +0100 (BST)

Guillermo:
> Is this so that package managers can alert users when they try to install
> packages with these conflicts?

No. It was to make it so that M. Caravia could build packages for Arch Linux.

Arch Linux has a system like /command, except that it doesn't have the
alternatives-like symbolic link idea and it has an oddball name from the 1970s.
 (-: I wasn't planning to cross the bridge of having things install outwith
/usr/local yet, but M. Caravia wanted that. However, when just taking the
existing setup and substituting /usr for /usr/local, xe had a list of conflicts
on Arch Linux. Since I had the shims package concept anyway, I extended it.

Guillermo:
> It seems that every program and program alias created by package/compile
> in ${src}/command/ is installed to some ${dest}/nosh-*/ directory, except the
> aliases disable, enable, preset, reset, show and show-json, so no binary
> packages will contain them. I'm not sure if this is intentional, and it is a
> minor
> thing, but I though I should mention it as well.

Only some of these sub-commands of system-control are available like that, and
in general only where something such as upstart compatibility (hence the start,
stop, and status aliases) requires it. These names are fairly central. Note
for starters that there is a completely different command named "reset" that is
in common use. And "enable" and "disable" are System 5 printer spool management
commands. (-:
Received on Tue Apr 18 2017 - 16:01:56 UTC