From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wine: install man page for wine executable
Date: Sun, 30 Apr 2023 11:32:04 +0200 [thread overview]
Message-ID: <20230430093204.gfzKXrZ0wReBXEtrkUDAJBJtWwKHFRASLcWUdE967FQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43664@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/pull/43664#issuecomment-1528979366
Comment:
I used `vinstall` to install the `wine.de.UTF-8.man`, `wine.fr.UTF-8.man` and `wine.pl.UTF-8.man` manuals. `vman` is unable to install them in the correct location because of the 'UTF-8' string in the filename, but this causes xlint to fail. They should be installed in `/usr/share/man/<lang>.UTF-8/man1` like how Wine installs the `winemaker` and `wineserver` manuals.
Should I just rename the manuals before calling `vman`?
next prev parent reply other threads:[~2023-04-30 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 4:50 [PR PATCH] " amak79
2023-04-30 4:47 ` amak79
2023-04-30 9:10 ` amak79
2023-04-30 9:11 ` [PR PATCH] [Updated] " amak79
2023-04-30 9:23 ` amak79
2023-04-30 9:32 ` amak79 [this message]
2023-04-30 9:45 ` amak79
2023-04-30 10:03 ` amak79
2023-04-30 18:16 ` classabbyamp
2023-05-01 4:37 ` amak79
2023-05-06 14:40 ` classabbyamp
2023-05-08 1:04 ` [PR PATCH] [Updated] " amak79
2023-05-08 1:49 ` [PR REVIEW] " classabbyamp
2023-05-08 2:12 ` [PR PATCH] [Updated] " amak79
2023-05-08 2:13 ` [PR REVIEW] " amak79
2023-05-08 3:39 ` [PR PATCH] [Merged]: " classabbyamp
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=20230430093204.gfzKXrZ0wReBXEtrkUDAJBJtWwKHFRASLcWUdE967FQ@z \
--to=amak79@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).