From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] problem with exim ebuild
Date: 17 Nov 2001 17:13:29 +0100 [thread overview]
Message-ID: <1006013609.2155.0.camel@zoidberg> (raw)
In-Reply-To: <20011111212545.2160f4e6.jnelson@jamponi.net>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
mån 2001-11-12 klockan 04.25 skrev Jon Nelson:
> Simple: It doesn't contain any manpages. Is there a policy that programs
> require manpages?
If the package doesn't contain any manpage I don't see any problem. I
don't think we should start using the scheme they use in Debian where
the package is broken if it doesn't have a manpages (imho this is just
lame).
So, if package doesn't contain any manpage I don't see no problem.
Regards,
Mikael Hallendal
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-11-17 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 21:22 [gentoo-dev] problem with exim ebuild Jon Nelson
2001-11-17 16:13 ` Mikael Hallendal [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=1006013609.2155.0.camel@zoidberg \
--to=hallski@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@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