From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Ulrich Mueller <ulm@gentoo.org>
Subject: Re: [gentoo-dev] Links to compressed files (was: gentoo-x86 commit in app-misc/mmv: ChangeLog mmv-1.01b_p15.ebuild)
Date: Wed, 26 May 2010 04:42:23 -0400 [thread overview]
Message-ID: <201005260442.24311.vapier@gentoo.org> (raw)
In-Reply-To: <19452.54616.365393.352938@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: Text/Plain, Size: 730 bytes --]
On Wednesday 26 May 2010 04:01:28 Ulrich Mueller wrote:
> >>>>> On Wed, 26 May 2010, Torsten Veller wrote:
> >> dosym mmv.1.gz /usr/share/man/man1/mcp.1.gz || die
> >> dosym mmv.1.gz /usr/share/man/man1/mln.1.gz || die
> >> dosym mmv.1.gz /usr/share/man/man1/mad.1.gz || die
> >
> > Is there a reliable/predictable way to create such links?
>
> Don't use a symlink, but create a short file with a groff .so request.
> See for example the egrep.1 man page, that just contains the one line:
>
> .so man1/grep.1
wonder if this would be a useful repoman check & recommendation. dare i grep
the tree to find all the existing miscreants ...
personally i prefer '.so grep.1' to avoid the redundancy ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-05-26 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100525173210.7F5C22CD19@corvid.gentoo.org>
2010-05-26 7:47 ` [gentoo-dev] Links to compressed files (was: gentoo-x86 commit in app-misc/mmv: ChangeLog mmv-1.01b_p15.ebuild) Torsten Veller
2010-05-26 7:58 ` [gentoo-dev] Links to compressed files Samuli Suominen
2010-05-26 8:01 ` [gentoo-dev] Links to compressed files (was: gentoo-x86 commit in app-misc/mmv: ChangeLog mmv-1.01b_p15.ebuild) Ulrich Mueller
2010-05-26 8:42 ` Mike Frysinger [this message]
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=201005260442.24311.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@gentoo.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