From: Tom Rymes <tom@rymes.net>
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 [thread overview]
Message-ID: <24D3CDF1-DEB6-4E5D-AB1C-6C14D30386E2@rymes.net> (raw)
In-Reply-To: <D09B9101-20B5-4F41-8836-0E775F12C647@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
I’d argue that the population of people who haven’t upgraded, but want nano is small enough that it’s a non-issue. Also, nano isn’t URGENT for anyone that might be unable to upgrade immediately. For most, though, just upgrade and it’s there.
Tom
> On Apr 28, 2022, at 2:44 PM, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
> Hey Michael,
>
> Removing in the future sounds fine.
>
> I was more worried I had done something wrong when submitting nano. Being my first I am skittish!
>
> Thanks!
> Jon
>
>> On Apr 28, 2022, at 1:09 PM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>
>> Hello Jon,
>>
>> This is a little bit of a dilemma now.
>>
>> 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 packages because that rarely happens that we remove something. And if we do so, we normally remove something that is not used by anyone.
>>
>> With nano, I could now just remove the package from the server, but then nobody 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. After that, they won’t have nano any more.
>>
>> 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 uninstall it, they can simply re-install it again.
>>
>> If we remove it in a couple of weeks, then that should be fine. People should 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 upgrade :)
>>
>> -Michael
>>
>>>> On 28 Apr 2022, at 19:00, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>
>>> Hi Peter,
>>>
>>> I see nano is now part of the core in CU 167. Yay!
>>>
>>> But it still appears in the Pakfire add-on list. Ugh!!
>>>
>>>
>>> Jon
>>>
>>>
>>> [root(a)ipfire ~] # pakfire list | grep -A3 nano
>>> Name: nano
>>> ProgVersion: 6.1
>>> Release: 41
>>>
>>> [root(a)ipfire ~] #
>>>
>>>
>>> <Screen Shot 2022-04-27 at 10.16.34 PM.png>
>>>
>>>
>>
>
prev parent reply other threads:[~2022-04-28 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <731D24A2-6EAC-4A33-B627-98FC6BEA7A77@gmail.com>
2022-04-28 18:09 ` Michael Tremer
2022-04-28 18:44 ` Jon Murphy
2022-04-28 19:07 ` Tom Rymes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24D3CDF1-DEB6-4E5D-AB1C-6C14D30386E2@rymes.net \
--to=tom@rymes.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox