public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jon Murphy <jcmurphy26@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Nano: Move nano editor from packages to core system
Date: Mon, 21 Mar 2022 16:20:26 -0500	[thread overview]
Message-ID: <CD96DDBE-D2D2-4B1C-B555-7EF07ABC9A4B@gmail.com> (raw)
In-Reply-To: <2cd3278b-bbee-c1fd-5790-4732cc12fe2f@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3456 bytes --]

Hey Peter!

This is my first patch so I am looking to learn!  (See below)


> On Mar 21, 2022, at 2:06 PM, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello *,
> 
> I just merged this patch into next, but since it was generated manually, I had to do
> the changes introduced by it myself manually.

Did I create the patch incorrectly?  Is there something I can do differently?

> 
>> Hello,
>> 
>> I personally do not count nano as an editor. There are so many things wrong with it :)
>> 
>> But if everyone wants this, I do not think that shipping ~444 KB of code will break the camel’s back.
> 
> Certainly not.
> 
>> 
>> Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>
>> 
>> -Michael
>> 
>> P.S. @Peter: Would you please make sure that pakfire drops the metadata of the package?

Same with this question - Is there something I can do differently?

> 
> Yes.
> 
> Thanks, and best regards,
> Peter Müller

Thank you!
Jon

> 
>> 
>>> On 21 Mar 2022, at 17:49, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi All,
>>> 
>>> On 21/03/2022 17:22, Peter Müller wrote:
>>>> Hello *,
>>>> 
>>>>> Hello,
>>>>> 
>>>>> How is everybody feeling about this?
>>>> I understand the motivation behind this. In my early days, I completely lacked any vim
>>>> skills, and found it pretty stressing to bring things back up after a crash while at the
>>>> same time frantically thinking "how to %&§#$ deal with this text editor?!".
>>>> 
>>>>> How many nano users do we have here?
>>> I am definitely one. I also use nano for working on my Arch Linux systems and adjust the default editor for things like visudo so it uses nano.
>>> 
>>> 
>>> Regards,
>>> Adolf.
>>>> Back then, nano would have helped me. Today, I am used to vim and would not experience
>>>> any benefit from nano being around on IPFire as well.
>>>> 
>>>> Nevertheless, I vote in favour of this patch, for reasons mentioned above.
>>>> 
>>>> Acked-by: Peter Müller <peter.mueller(a)ipfire.org>
>>>> 
>>>> Thanks, and best regards,
>>>> Peter Müller
>>>> 
>>>>> -Michael
>>>>> 
>>>>>> On 17 Mar 2022, at 17:06, Jon Murphy <jon.murphy(a)ipfire.org> wrote:
>>>>>> 
>>>>>> - this will not change the default editor `vim`
>>>>>> 
>>>>>> Signed-off-by: Jon Murphy <jon.murphy(a)ipfire.org>
>>>>>> ---
>>>>>> config/rootfiles/{packages => common}/nano | 0
>>>>>> lfs/nano                                   | 7 +++----
>>>>>> 2 files changed, 3 insertions(+), 4 deletions(-)
>>>>>> rename config/rootfiles/{packages => common}/nano (100%)
>>>>>> 
>>>>>> diff --git a/config/rootfiles/packages/nano b/config/rootfiles/common/nano
>>>>>> similarity index 100%
>>>>>> rename from config/rootfiles/packages/nano
>>>>>> rename to config/rootfiles/common/nano
>>>>>> diff --git a/lfs/nano b/lfs/nano
>>>>>> index df994364f..85be014ee 100644
>>>>>> --- a/lfs/nano
>>>>>> +++ b/lfs/nano
>>>>>> @@ -32,12 +32,11 @@ DL_FILE    = $(THISAPP).tar.xz
>>>>>> DL_FROM    = $(URL_IPFIRE)
>>>>>> DIR_APP    = $(DIR_SRC)/$(THISAPP)
>>>>>> TARGET     = $(DIR_INFO)/$(THISAPP)
>>>>>> -PROG       = nano
>>>>>> -PAK_VER    = 41
>>>>>> 
>>>>>> -DEPS       = ""
>>>>>> 
>>>>>> -SERVICES   =
>>>>>> 
>>>>>> ###############################################################################
>>>>>> # Top-level Rules
>>>>>> -- 
>>>>>> 2.30.2
>>>>>> 
>>> 
>>> -- 
>>> Sent from my laptop
>> 


  reply	other threads:[~2022-03-21 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 17:06 Jon Murphy
2022-03-21 16:09 ` Michael Tremer
2022-03-21 16:22   ` Peter Müller
2022-03-21 17:49     ` Adolf Belka
2022-03-21 18:52       ` Michael Tremer
2022-03-21 19:06         ` Peter Müller
2022-03-21 21:20           ` Jon Murphy [this message]
2022-03-24  9:52             ` Peter Müller
2022-03-21 17:15   ` Matthias Fischer
2022-03-21 18:55   ` Tom Rymes
2022-03-22  1:01   ` Paul Simmons
2022-03-22 10:49     ` Michael Tremer

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=CD96DDBE-D2D2-4B1C-B555-7EF07ABC9A4B@gmail.com \
    --to=jcmurphy26@gmail.com \
    --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