public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [RFC] EAPI 2 Draft
Date: Sat, 06 Sep 2008 12:43:12 +0100	[thread overview]
Message-ID: <g9tqmf$ncd$1@ger.gmane.org> (raw)
In-Reply-To: 20080905110738.5c02a521@terra.solaris

Christian Faulhammer wrote:

> Zac Medico <zmedico@gentoo.org>:
>> Both approaches are essentially equivalent but it's a little simpler
>> for ebuild writer if they don't have to customize the output file
>> name.
> 
>  One needs exceptions for all kind of systems, for example I had to
> workaround Trac which adds ?format=raw to a tarball URI.  There seems
> to be a solution in Trac as the guys from fedarahosted fixed the two I
> needed (tmpwatch, mlocate).  So the -> operator is quite useful and I
> agree with David that the functionality is doubled.
> 
Clearly src-uri transformation is useful. Others have given examples of how
it would be useful to an eclass. Irrespective of how the actual transform
is done in the ;sf=tbz2 case, both _are_ valid use-cases.

As such I don't see any reason not to put it in the EAPI. Future extensions
can be trialled in eutils, and these can both be allowed syntax for other
package managers to comply with (one implementation has already been given)
and ebuild devs to feel comfortable using in the Gentoo tree. Why slow the
innovation down? It's good enough for use as-is.





  reply	other threads:[~2008-09-06 11:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 22:58 [gentoo-dev] [RFC] EAPI 2 Draft Zac Medico
2008-09-05  6:47 ` David Leverton
2008-09-05  7:19   ` Zac Medico
2008-09-05  7:29     ` David Leverton
2008-09-05  7:39       ` Zac Medico
2008-09-05  8:32         ` Fernando J. Pereda
2008-09-05 12:14           ` Robert Buchholz
2008-09-05 12:30             ` Mike Auty
2008-09-05 13:20               ` Robert Buchholz
2008-09-05 12:30             ` Mike Auty
2008-09-05  9:16         ` Alec Warner
2008-09-05 15:58           ` Petteri Räty
2008-09-06 20:01           ` [gentoo-dev] " Markus Ullmann
2008-09-08 21:25         ` [gentoo-dev] " Donnie Berkholz
2008-09-05  9:07     ` [gentoo-dev] " Christian Faulhammer
2008-09-06 11:43       ` Steve Long [this message]
2008-09-06 17:14         ` Thomas Anderson
2008-09-08 21:48           ` [gentoo-dev] " Steve Long
2008-09-06 19:03         ` [gentoo-dev] " Alec Warner
2008-09-08 21:46           ` [gentoo-dev] " Steve Long
2008-09-08 23:46             ` Alec Warner
2008-09-05 19:00 ` [gentoo-dev] " Bo Ørsted Andresen

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='g9tqmf$ncd$1@ger.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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