Re: Please release nano under less restrictive license so we can use it

[akierig]

On 2023-04-29 at 06:12 (-0500) Gur Telem wrote:

What puzzles me is what's keeping you from using MacPorts (https://ports.macports.org/port/nano/) or Homebrew to install it?

My job requires working on multiple machines, many hosts and servers.

I would need to modify the PATHs for all users on all machines and install both homebrew and then nano. All for a very basic use case.

One other potential solution for you (and how I avoid using nano 2.3.1 on my job's RHEL 7 machines) is to compile nano with `./configure LDFLAGS=-static` on a local machine with the appropriate dependencies installed, then pop it on to the server with sftp.

I've not had time to test it but this *might* work. `CC="clang" ./configure LDFLAGS=-static`.

Another option in the same vein would be to use (micro https://github.com/zyedidia/micro and some key binding changes (https://ttm.sh/W7s.txt) at `~/.config/micro/bindings.json`) but this would involve grabbing the latest release binary from Github.

Finally, you could always ask them to start packaging Joe's Own Editor (joe) and running it as jpico. joe is under GPL2.

In either case not the easiest but it might make your life a little bit easier. Should've thought to suggest this earlier. In any case definitely easier than convincing the FSF to relicense.

kind regards,

ander