From: ~eschwartz <eschwartz@git.sr.ht>
To: bzip2-devel@sourceware.org
Cc: eschwartz93@gmail.com
Subject: [PATCH bzip2 4/6] make a couple program aliases symlinks instead of copies
Date: Fri, 03 Jun 2022 00:48:15 -0400 [thread overview]
Message-ID: <165475384722.17277.18269615533597437835-3@git.sr.ht> (raw)
In-Reply-To: <165475384722.17277.18269615533597437835-0@git.sr.ht>
From: Eli Schwartz <eschwartz93@gmail.com>
Some programs are installed one way, some are installed the other way.
Be consistent and always use symlinks.
---
Makefile.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Makefile.in b/Makefile.in
index 6631733..76dfe9a 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -82,8 +82,8 @@ install: bzip2 bzip2recover
if ( test ! -d $(DESTDIR)$(mandir)/man1 ) ; then mkdir -p $(DESTDIR)$(mandir)/man1 ; fi
if ( test ! -d $(DESTDIR)$(includedir) ) ; then mkdir -p $(DESTDIR)$(includedir) ; fi
cp -f bzip2 $(DESTDIR)$(bindir)/bzip2
- cp -f bzip2 $(DESTDIR)$(bindir)/bunzip2
- cp -f bzip2 $(DESTDIR)$(bindir)/bzcat
+ ln -s -f bzip2 $(DESTDIR)$(bindir)/bunzip2
+ ln -s -f bzip2 $(DESTDIR)$(bindir)/bzcat
cp -f bzip2recover $(DESTDIR)$(bindir)/bzip2recover
chmod a+x $(DESTDIR)$(bindir)/bzip2
chmod a+x $(DESTDIR)$(bindir)/bunzip2
--
2.34.2
next prev parent reply other threads:[~2022-06-09 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 3:45 [PATCH bzip2 1/6] install relative symlinks ~eschwartz
2022-06-03 4:20 ` [PATCH bzip2 2/6] port the build configuration to autoconf ~eschwartz
2022-06-09 5:56 ` Eli Schwartz
2022-06-03 4:48 ` ~eschwartz [this message]
2022-06-03 4:54 ` [PATCH bzip2 5/6] install man page symlinks for a couple more symlinked commands ~eschwartz
2022-06-03 5:09 ` [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2 ~eschwartz
2022-06-09 5:52 ` Eli Schwartz
2022-10-23 16:03 ` Sam James
2022-06-09 4:50 ` [PATCH bzip2 3/6] shared Makefile: add install rule ~eschwartz
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=165475384722.17277.18269615533597437835-3@git.sr.ht \
--to=eschwartz@git.sr.ht \
--cc=bzip2-devel@sourceware.org \
--cc=eschwartz93@gmail.com \
--cc=eschwartz@archlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).