From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-devhelp@lists.gentoo.org
Cc: James Cloos <cloos@jhcloos.com>
Subject: Re: [gentoo-devhelp] dodoc vs directories
Date: Sat, 18 Feb 2012 14:40:31 +0100 [thread overview]
Message-ID: <4F3FAA4F.1010208@gentoo.org> (raw)
In-Reply-To: <m3ipj5gmk4.fsf@carbon.jhcloos.org>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
James Cloos schrieb:
> It seems that dodoc recently has lost recusivity in portage master.
Unless you found something special with EAPI-4, then there is nothing
lost. dodoc never had the ability to work on directories in EAPI<4.
There was just a bug in portage, which did not let dodoc die, when it
was called on a directory. This now should, according to the mentioned
bug 356389, show a QA warning and at some later point die as it should
have done from the beginning.
>
> Several ebuilds (including in the main tree) now fail because of that.
Please give me some common example for such a failure.
>
> Bug https://bugs.gentoo.org/show_bug.cgi?id=356389 implies that the goal
> is only to qawarn, not error, when passed a directory. And dodoc itself
> seems to work that way.
So if dodoc does just qawarn, how should ebuilds now fail with dodoc
called on directories?
>
> But doins does not (cf:
>
> :; grep -C3 '$x is a directory' /usr/lib/portage/bin/ebuild-helpers/doins
>
> for the details).
doins was never ment to work on directories, unless you used the -r switch.
>
> Is this a bug in portage or should I submit bugs, blocking 356389, for
> each failure?
I currently cannot really see your problem, maybe you mixed some facts
about dodoc and doins? Otherwise, please clarify this.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 380 bytes --]
next prev parent reply other threads:[~2012-02-18 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 21:46 [gentoo-devhelp] dodoc vs directories James Cloos
2012-02-18 13:40 ` Thomas Sachau [this message]
2012-02-18 17:56 ` James Cloos
2012-02-18 19:05 ` Thomas Sachau
2012-02-20 6:13 ` James Cloos
2012-02-23 20:56 ` Thomas Sachau
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=4F3FAA4F.1010208@gentoo.org \
--to=tommy@gentoo.org \
--cc=cloos@jhcloos.com \
--cc=gentoo-devhelp@lists.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