From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] DEFAULT_* proposal
Date: Sun, 09 Nov 2008 18:28:39 +0300 [thread overview]
Message-ID: <1226244519.27750.212.camel@localhost> (raw)
In-Reply-To: <20081109140437.GA5200@spoc>
Well for myself I found compromise. Although in both proposals as I see
you've omitted part where you'll discuss how you are going to implement
this feature, implementing this feature as eclass addresses most of my
concerns, since:
1. ebuild's syntax does not change
2. people will have to inherit some.eclass to use them and thus will do
this only when it's really saves time/efforts
I've dropped all other answers I was going to give you since I started
to feel that this is just another cycle. We can discuss them off list if
necessary. :)
--
Peter.
next prev parent reply other threads:[~2008-11-09 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 22:20 [gentoo-dev] DEFAULT_* proposal Thomas Anderson
2008-11-09 3:10 ` Thomas Sachau
2008-11-09 12:39 ` Peter Volkov
2008-11-09 14:04 ` Thomas Anderson
2008-11-09 15:28 ` Peter Volkov [this message]
2008-11-09 15:02 ` Santiago M. Mola
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=1226244519.27750.212.camel@localhost \
--to=pva@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