From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Re: Nano: Move nano editor from packages to core system - new issue Date: Thu, 28 Apr 2022 15:07:59 -0400 Message-ID: <24D3CDF1-DEB6-4E5D-AB1C-6C14D30386E2@rymes.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3897753140749121435==" List-Id: --===============3897753140749121435== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I=E2=80=99d argue that the population of people who haven=E2=80=99t upgraded,= but want nano is small enough that it=E2=80=99s a non-issue. Also, nano isn= =E2=80=99t URGENT for anyone that might be unable to upgrade immediately. For= most, though, just upgrade and it=E2=80=99s there. Tom > On Apr 28, 2022, at 2:44 PM, Jon Murphy wrote: >=20 > =EF=BB=BFHey Michael, >=20 > Removing in the future sounds fine. >=20 > I was more worried I had done something wrong when submitting nano. Being = my first I am skittish! >=20 > Thanks! > Jon >=20 >> On Apr 28, 2022, at 1:09 PM, Michael Tremer = wrote: >>=20 >> Hello Jon, >>=20 >> This is a little bit of a dilemma now. >>=20 >> So, there is only one tree for packages. I normally take all packages from= the latest build and publish those. However, I do not manually delete packag= es because that rarely happens that we remove something. And if we do so, we = normally remove something that is not used by anyone. >>=20 >> With nano, I could now just remove the package from the server, but then n= obody who has not yet updated to the latest release can install it any more. = If I leave it on the server, people can install it, and then uninstall it. Af= ter that, they won=E2=80=99t have nano any more. >>=20 >> I would therefore like to leave it on the server for a little bit longer, = because although the second option has the disadvantage that people might uni= nstall it, they can simply re-install it again. >>=20 >> If we remove it in a couple of weeks, then that should be fine. People sho= uld upgrade soon and we generally do not support older releases. However, the= release is only a day ago, and we should give people a little time to upgrad= e :) >>=20 >> -Michael >>=20 >>>> On 28 Apr 2022, at 19:00, Jon Murphy wrote: >>>=20 >>> Hi Peter, >>>=20 >>> I see nano is now part of the core in CU 167. Yay! >>>=20 >>> But it still appears in the Pakfire add-on list. Ugh!! >>>=20 >>>=20 >>> Jon >>>=20 >>>=20 >>> [root(a)ipfire ~] # pakfire list | grep -A3 nano >>> Name: nano >>> ProgVersion: 6.1 >>> Release: 41 >>>=20 >>> [root(a)ipfire ~] #=20 >>>=20 >>>=20 >>> >>>=20 >>>=20 >>=20 >=20 --===============3897753140749121435==--