From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Nano: Move nano editor from packages to core system
Date: Mon, 21 Mar 2022 16:09:50 +0000 [thread overview]
Message-ID: <1F3BD669-ED85-458C-9EF3-562649E199FA@ipfire.org> (raw)
In-Reply-To: <20220317170628.1362568-1-jon.murphy@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Hello,
How is everybody feeling about this?
How many nano users do we have here?
-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
>
next prev parent reply other threads:[~2022-03-21 16:09 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 [this message]
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
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=1F3BD669-ED85-458C-9EF3-562649E199FA@ipfire.org \
--to=michael.tremer@ipfire.org \
--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