From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vala.eclass: change vala_src_prepare behavior when USE=-vala
Date: Thu, 20 Sep 2012 19:56:25 +0200 [thread overview]
Message-ID: <1348163785.27524.37.camel@belkin4> (raw)
In-Reply-To: <20120920145212.61ed6d2a@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
El jue, 20-09-2012 a las 14:52 +0100, Ciaran McCreesh escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 20 Sep 2012 09:13:40 -0400
> Ian Stakenvicius <axs@gentoo.org> wrote:
> > PMS may not need to be fixed, just the spec
>
> PMS is the spec, and it doesn't need fixing, since it accurately
> reflects the situation we're dealing with.
>
> - --
> Ciaran McCreesh
What is preventing us from specifying current behavior in PMS? Current
behavior is already working for ages and being used in the tree for a
long time, then, the clear way to go is to document it and, if it needs
to change in the future, specify new behavior on a newer eapi.
It's the simplest solution, it should work, would prevent us from need
to move current eclasses/ebuilds to worse ways of handling this to later
revert that work.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-20 17:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHG43MsUfVPXqqv-zRKH1spToR=kKQFYNfCxXjiewr=FeaV4qg@mail.gmail.com>
[not found] ` <1347928029.24984.27.camel@rook>
2012-09-19 19:26 ` [gentoo-dev] vala.eclass: change vala_src_prepare behavior when USE=-vala Alexandre Rostovtsev
2012-09-19 19:37 ` Ciaran McCreesh
2012-09-19 20:33 ` Ian Stakenvicius
2012-09-19 20:42 ` Ciaran McCreesh
2012-09-19 21:03 ` Michał Górny
2012-09-19 21:14 ` Ciaran McCreesh
2012-09-19 21:24 ` Michał Górny
2012-09-19 21:31 ` Ciaran McCreesh
2012-09-19 21:39 ` Michał Górny
2012-09-19 21:51 ` Ciaran McCreesh
2012-09-19 22:13 ` Michał Górny
2012-09-19 22:18 ` Ciaran McCreesh
2012-09-19 22:30 ` Michał Górny
2012-09-19 22:45 ` Ciaran McCreesh
2012-09-19 19:46 ` Michał Górny
2012-09-20 6:14 ` Alexandre Rostovtsev
2012-09-20 6:43 ` Pacho Ramos
2012-09-20 7:33 ` Alexandre Rostovtsev
2012-09-20 17:52 ` Pacho Ramos
2012-09-20 17:55 ` Ciaran McCreesh
2012-09-20 7:41 ` Michał Górny
2012-09-20 13:13 ` Ian Stakenvicius
2012-09-20 13:52 ` Ciaran McCreesh
2012-09-20 14:14 ` Ian Stakenvicius
2012-09-20 14:26 ` Ciaran McCreesh
2012-09-20 14:40 ` Ian Stakenvicius
2012-09-20 17:58 ` Pacho Ramos
2012-09-20 18:12 ` Michael Mol
2012-09-20 18:23 ` Ian Stakenvicius
2012-09-20 18:24 ` Ciaran McCreesh
2012-09-20 19:22 ` Ian Stakenvicius
2012-09-20 19:31 ` Ciaran McCreesh
2012-09-20 19:47 ` Ian Stakenvicius
2012-09-20 19:47 ` Ian Stakenvicius
2012-09-21 19:01 ` Pacho Ramos
2012-09-22 8:07 ` Pacho Ramos
2012-09-20 17:56 ` Pacho Ramos [this message]
2012-09-20 17:54 ` Pacho Ramos
2012-09-20 17:55 ` Ciaran McCreesh
2012-09-20 18:13 ` Pacho Ramos
2012-09-20 18:15 ` Ciaran McCreesh
2012-09-20 18:33 ` Michael Mol
2012-09-20 8:10 ` Ciaran McCreesh
2012-09-20 18:02 ` Pacho Ramos
2012-09-20 18:11 ` Ciaran McCreesh
2012-09-20 22:42 ` [gentoo-dev] " Duncan
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=1348163785.27524.37.camel@belkin4 \
--to=pacho@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