GNU Nano: Upstream has released v3.0

https://www.nano-editor.org/news.php

$ snap info nano-editor
name:      nano-editor
summary:   The nano text editor
publisher: Roderick Smith (rws)
contact:   https://www.nano-editor.org/
license:   GPL-3.0
description: |
  small, friendly text editor inspired by Pico GNU nano is an easy-to-use text
  editor originally designed as a replacement for Pico, the ncurses-based editor
  from the non-free mailer package Pine (itself now available under the Apache
  License as Alpine).
snap-id: 0lND35jIppnjMdrXfZRpjGCMMWhSJ9z0
channels:                    
  stable:    2.6.3 (1) 638kB -
  candidate: 2.6.3 (1) 638kB -
  beta:      2.6.3 (1) 638kB -
  edge:      2.6.3 (1) 638kB -

Can the snap be updated as well?

UPDATE: If the nano snap name is not taken by the upstream, can I take it instead and maintain it using the snapcrafters protocol?

UPDATE 2: I’ve got the nano snap name, will implement it in the near future.

1 Like

As usual, I’m having trouble tracking down the source repo for a snap.

In this case, it’s not in Nano’s main codebase: http://git.savannah.gnu.org/cgit/nano.git/tree/ nor the Snapcrafter’s Repo: https://github.com/snapcrafters

2 Likes

Possibly this person? (though I can’t find a nano snap source repo under that account)

1 Like

I think nano should use classic confinement, otherwise it’s useless for editing system config files.

2 Likes

IMHO I believe snapcraft should allow both recipes, with and without classic confinement, to coexist.

Just want to inform you it is up now: The (UNOFFICIAL) nano Text Editor