From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] coreutils: drop patch that unconditionally mangles manpages
Date: Thu, 7 Aug 2014 19:35:32 +0200 [thread overview]
Message-ID: <20140807173532.GX14848@jama> (raw)
In-Reply-To: <53E383AA.9010202@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
On Thu, Aug 07, 2014 at 09:48:26AM -0400, Paul Gortmaker wrote:
> On 14-08-07 01:33 AM, Koen Kooi wrote:
> >
> > Op 6 aug. 2014, om 22:38 heeft Paul Gortmaker <paul.gortmaker@windriver.com> het volgende geschreven:
> >
> >> commit 841ec528ec04e64bd09ff10f8d9ad2d6e3aac05d ("coreutils: update
> >> to upstream version 9.21") added a patch which bypassed the check
> >> for perl and hence defaults to using the dummy man page for all
> >> of the coreutils manpages. This results in all manpages looking like:
> >>
> >> NAME
> >> chmod - a GNU coreutils 8.22 program
> >>
> >> DESCRIPTION
> >> OOOPS! Due to the lack of perl on the build system, we were unable to
> >> create a proper manual page for chmod.
> >>
> >> It is unclear why the test was disabled, but since it clearly
> >> causes the manpages to be useless, we need to drop this patch.
> >
> > That all might be true, but DEPENDS doesn't list 'perl' or 'perl-native', so this commit is wrong.
>
> Wrong might be overstated. The patch unconditionally disables a
> _check_ for perl. So if perl is there, it is used; if it is absent,
> it is not. Given that there really is no excuse for shipping
> broken manpages, one could argue that a DEPENDS on perl-native
> is sensible, and if that is what it takes to get the broken patch
> dropped, I'll add one.
undeterministic build results mean it's broken
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-07 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 20:38 [PATCH] coreutils: drop patch that unconditionally mangles manpages Paul Gortmaker
2014-08-07 5:33 ` Koen Kooi
2014-08-07 13:48 ` Paul Gortmaker
2014-08-07 17:35 ` Martin Jansa [this message]
2014-08-07 8:42 ` ChenQi
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=20140807173532.GX14848@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
/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