From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Allow variable refs in HOMEPAGE
Date: Fri, 4 Aug 2017 14:02:31 +0000 [thread overview]
Message-ID: <20170804140231.GD22159@stuge.se> (raw)
In-Reply-To: <e7a1f094-c9c0-fbc5-7fd7-7aad4e89e97c@gentoo.org>
Michael Orlitzky wrote:
> All this is to say that "easy to read" is in the eye of the beholder.
> For ebuilds in the tree, the beholder is usually the maintainer, which
> is why I think the choice should be left up to him.
I think what mgorny says is that locality of ebuilds is an important factor.
> Our ebuilds are bash programs, and in source code, "as little
> duplication as possible" is a strong contributor to "easy to read."
Here's an idea: Could a little bit of automated (but obviously checked!)
de-duplication be made [an optional] part of adding an ebuild into the
tree, and please everyone?
//Peter
next prev parent reply other threads:[~2017-08-04 14:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 15:33 [gentoo-dev] Allow variable refs in HOMEPAGE Mike Gilbert
2017-08-03 15:54 ` Michał Górny
2017-08-03 20:56 ` Mike Gilbert
2017-08-03 23:10 ` Sam Jorna
2017-08-03 17:21 ` Jonas Stein
2017-08-07 14:05 ` Kent Fredric
2017-08-03 18:21 ` Michael Orlitzky
2017-08-03 18:32 ` Michał Górny
2017-08-03 18:57 ` Mike Gilbert
2017-08-03 19:12 ` Michael Orlitzky
2017-08-03 19:39 ` Mike Gilbert
2017-08-03 19:56 ` Michael Orlitzky
2017-08-03 20:46 ` Mike Gilbert
2017-08-03 22:33 ` Ulrich Mueller
2017-08-04 3:24 ` Michael Orlitzky
2017-08-04 6:50 ` Michał Górny
2017-08-04 13:43 ` Michael Orlitzky
2017-08-04 14:02 ` Peter Stuge [this message]
2017-08-04 6:51 ` Ulrich Mueller
2017-08-03 19:39 ` Ulrich Mueller
2017-08-03 19:34 ` Ulrich Mueller
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=20170804140231.GD22159@stuge.se \
--to=peter@stuge.se \
--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