From: Jim Ramsay <lack@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Default blank lines for error, elog, einfo, etc
Date: Wed, 11 Jun 2008 19:45:57 -0400 [thread overview]
Message-ID: <20080611194557.560e2dbf@altair.jimramsay.com> (raw)
In-Reply-To: <4849BD55.7050205@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Vlastimil Babka <caster@gentoo.org> wrote:
> I would prefer something that
> doesn't add extra lines to ebuild.
I think I would disagree with you here. I think that having a special
'eblank' or 'eseparator' command is much more readable in an ebuild.
Consider:
pkg_postinst() {
elog "Knock knock"
eblank
ewarn "Who's there?"
eblank
elog "Interrupting Cow"
eblank
ewarn "Interrup..."
elog "Moo!"
}
Versus:
pkg_postinst() {
elog -p "Knock knock"
ewarn "Who's there?"
elog -pt "Interrupting Cow"
ewarn "Interrup..."
elog "Moo!"
}
I think that in the former case it's much more obvious how the actual
output is going to look. If the cost is an ebuild that's 3 lines
longer, I think that's reasonable.
--
Jim Ramsay
Gentoo/Linux Developer (rox,gkrellm)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-11 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 21:12 [gentoo-dev] Default blank lines for error, elog, einfo, etc William L. Thomson Jr.
2008-06-04 21:31 ` Joe Peterson
2008-06-05 0:45 ` [gentoo-dev] " Ryan Hill
2008-06-05 0:52 ` William L. Thomson Jr.
2008-06-05 0:59 ` William L. Thomson Jr.
2008-06-05 1:40 ` Joe Peterson
2008-06-06 22:42 ` Vlastimil Babka
2008-06-06 23:31 ` William L. Thomson Jr.
2008-06-07 0:07 ` Joe Peterson
2008-06-07 0:22 ` Vlastimil Babka
2008-06-11 23:45 ` Jim Ramsay [this message]
2008-06-15 10:02 ` Peter Volkov
2008-06-15 11:19 ` Benedikt Morbach
2008-06-15 13:14 ` Peter Volkov
2008-06-15 13:16 ` Joe Peterson
2008-06-16 12:34 ` Jim Ramsay
2008-06-16 16:06 ` Duncan
2008-06-16 16:41 ` Joe Peterson
2008-06-16 17:01 ` Duncan
2008-06-16 17:08 ` William L. Thomson Jr.
2008-06-16 12:36 ` Jim Ramsay
2008-06-16 17:05 ` William L. Thomson Jr.
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=20080611194557.560e2dbf@altair.jimramsay.com \
--to=lack@gentoo.org \
--cc=gentoo-dev@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