add prt-get.aliases.5 to the install targets

This commit is contained in:
John McQuah 2024-09-08 12:44:39 +00:00
parent 074326db2c
commit d9df037be0
2 changed files with 16 additions and 12 deletions

View File

@ -19,7 +19,7 @@ install-conf:
install-man:
mkdir -p $(DESTDIR)$(MANDIR)/man5
mkdir -p $(DESTDIR)$(MANDIR)/man8
install -m 644 doc/prt-get.conf.5 $(DESTDIR)$(MANDIR)/man5
install -m 644 doc/prt-get.aliases.5 doc/prt-get.conf.5 $(DESTDIR)$(MANDIR)/man5
install -m 644 doc/prt-get.8 doc/prt-cache.8 $(DESTDIR)$(MANDIR)/man8
install-bin: prtget
@ -35,6 +35,7 @@ uninstall:
rm -f $(DESTDIR)$(MANDIR)/man8/prt-get.8
rm -f $(DESTDIR)$(MANDIR)/man8/prt-cache.8
rm -f $(DESTDIR)$(MANDIR)/man5/prt-get.conf.5
rm -f $(DESTDIR)$(MANDIR)/man5/prt-get.aliases.5
rm -f $(DESTDIR)$(CONFDIR)/prt-get.conf
rm -f $(DESTDIR)$(CONFDIR)/prt-get.aliases
rm -f $(DESTDIR)$(PREFIX)/share/bash_completion/completions/prt-get

View File

@ -29,21 +29,24 @@ Every line is of the form
.LP
where <dep1>, <dep2>, ... <depN> (separated by whitespace) are the dependencies that are
considered satisfied when <alternative> is installed. For example, you might combine llvm, clang,
and compiler-rt into one port (as OpenBSD does), call it llvm-toolchain, and then write the line
and compiler\-rt into one port (as OpenBSD does), call it llvm\-toolchain, and then write the line
.IP
.B
llvm-toolchain: llvm clang compiler-rt
llvm\-toolchain: llvm clang compiler\-rt
.LP
which will prevent \fBprt\-get\fP from trying to install the standalone package \fBclang\fP when resolving
the dependencies of, say, \fBobjfw\fP.
which will prevent \fBprt\-get\fP from trying to install the standalone package clang when
resolving the dependencies of, say, objfw. This line will also prevent
\fBprt\-get listorphans\fP from reporting llvm\-toolchain as \(dqsafe for removal\(dq, if an
installed port depends on llvm, clang, or compiler\-rt.
.LP
You probably do not want to have the same alternative appearing more than once in \fBprt\-get.aliases\fP.
Later lines overwrite earlier lines, so only the final appearance of any particular alternative will be
considered by \fBprt\-get\fP. One possible use\-case for multiple appearances of <alternative> is if
the configuration of <alternative> is still in flux, and you are not yet sure how many ports it can serve as
a substitute for. Reordering the lines that start with \(dq<alternative>: \(dq will let you switch
between the different configurations, to quickly test the extent to which <alternative> is a drop-in
replacement for the maintainer-provided dependencies.
You probably do not want to have the same alternative appearing more than once in
\fBprt\-get.aliases\fP. Later lines overwrite earlier lines, so only the final appearance of any
particular alternative will be considered by \fBprt\-get\fP. One possible use\-case for multiple
appearances of <alternative> is if the configuration of <alternative> is still in flux, and
you are not yet sure how many ports it can serve as a substitute for. Reordering the lines that
start with \(dq<alternative>: \(dq will let you switch quickly among the different
configurations, to determine the extent to which <alternative> is a drop-in replacement for
dependencies expected by the port maintainers.
.SH "AUTHORS"
John McQuah <jmcquah at disroot dot org>
.SH "SEE ALSO"