From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: s6*: updating the whole stack of packages.
Date: Thu, 08 Feb 2024 19:40:30 +0100 [thread overview]
Message-ID: <20240208184030.0CCFE2BE7D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48582@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
New comment by mobinmob on void-packages repository
https://github.com/void-linux/void-packages/pull/48582#issuecomment-1934724927
Comment:
You can add the following to post_install() to fix the file conflicts:
```
mv "${DESTDIR}"/usr/bin/init "${DESTDIR}"/etc/66/init
mv "${DESTDIR}"/usr/share/man/man1/start.1 \
"${DESTDIR}"/usr/share/man/man1/66_start.1
mv "${DESTDIR}"/usr/share/man/man1/tree.1 \
"${DESTDIR}"/usr/share/man/man1/66_tree.1
```
The manpages can be all renamed to `66_$manpage` or `66-$manpage`.
next prev parent reply other threads:[~2024-02-08 18:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 15:51 [PR PATCH] " dataCobra
2024-02-07 16:10 ` [PR PATCH] [Updated] " dataCobra
2024-02-07 16:48 ` dataCobra
2024-02-07 16:56 ` dataCobra
2024-02-07 17:00 ` dataCobra
2024-02-07 17:03 ` dataCobra
2024-02-07 18:42 ` mobinmob
2024-02-07 18:44 ` mobinmob
2024-02-07 19:05 ` mobinmob
2024-02-08 6:39 ` [PR PATCH] [Updated] " dataCobra
2024-02-08 18:40 ` mobinmob [this message]
2024-02-10 9:36 ` dataCobra
2024-02-10 10:36 ` dataCobra
2024-02-10 10:38 ` dataCobra
2024-02-10 10:39 ` dataCobra
2024-02-10 10:44 ` dataCobra
2024-02-17 13:37 ` [PR PATCH] [Updated] " dataCobra
2024-02-17 13:53 ` dataCobra
2024-02-17 14:13 ` mobinmob
2024-02-17 14:19 ` mobinmob
2024-05-18 1:46 ` github-actions
2024-06-01 1:50 ` [PR PATCH] [Closed]: " github-actions
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=20240208184030.0CCFE2BE7D@inbox.vuxu.org \
--to=mobinmob@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).