From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. db27cae56e627a887159c46198d9141be760b777
Date: Sat, 09 Apr 2022 10:45:35 +0000 [thread overview]
Message-ID: <4KbBbh0376z2xWG@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via db27cae56e627a887159c46198d9141be760b777 (commit)
from 4b8ae872584947c0527eb5f76f06444f7b060cb4 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit db27cae56e627a887159c46198d9141be760b777
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sat Apr 9 10:44:10 2022 +0000
gzip: Symlink /usr/bin/zless to /usr/bin/zmore
gzip 1.12 no longer features zless. For convenience reasons, symlink
/usr/bin/zless to /usr/bin/zmore, so users won't need to relearn any
commands they were previously used to.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/gzip | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/gzip b/lfs/gzip
index 809c6a91f..c669c235f 100644
--- a/lfs/gzip
+++ b/lfs/gzip
@@ -84,7 +84,8 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && make install
ifeq "$(ROOT)" ""
mv -v /bin/{gzexe,zcmp,zdiff,zegrep} /usr/bin
- mv -v /bin/{zfgrep,zforce,zgrep,zless,zmore,znew} /usr/bin
+ mv -v /bin/{zfgrep,zforce,zgrep,zmore,znew} /usr/bin
+ ln -s /usr/bin/zmore /usr/bin/zless
endif
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-04-09 10:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4KbBbh0376z2xWG@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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