From: James Broadhead <jamesbroadhead@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFD : .ebuild is only bash
Date: Mon, 12 Mar 2012 22:55:45 +0000 [thread overview]
Message-ID: <CA+hid6H=tGqtXzQOt2PYA8wD26a0OQNGN7sScZWP96px6Tae3w@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFCXHXcRD9dquP7L97_upTGD6VzBktW5XV=+Cv7MTvSGeA@mail.gmail.com>
On 12 March 2012 22:37, Kent Fredric <kentfredric@gmail.com> wrote:
>
> Can somebody present a real ( or even theoretical ) problem that could
> arise from having the EAPI in the filename that isn't some abstract
> hand-waving?
>
> Not trying to be a troll here, but really, I still haven't seen any.
This isn't a real-world problem, but we're arguably over-loading too
much information into the filename already;
- package name
- package version
- ebuild revision
- (EAPI?)
next prev parent reply other threads:[~2012-03-12 22:56 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAATnKFD=9VEkpUcABbhHbAu96Qn+dP+YEuUu2YCqDUNKUxe+Cw@mail.gmail.com>
2012-03-12 15:57 ` [gentoo-dev] RFD : .ebuild is only bash Kent Fredric
2012-03-12 15:59 ` Ciaran McCreesh
2012-03-12 16:51 ` Rich Freeman
2012-03-12 17:05 ` Ulrich Mueller
2012-03-12 17:12 ` Ciaran McCreesh
2012-03-12 17:17 ` Michael Orlitzky
2012-03-12 17:22 ` Ciaran McCreesh
2012-03-12 17:30 ` Zac Medico
2012-03-12 17:22 ` Zac Medico
2012-03-12 18:00 ` Ulrich Mueller
2012-03-12 18:04 ` Ciaran McCreesh
2012-03-12 18:17 ` Ulrich Mueller
2012-03-12 18:28 ` Ciaran McCreesh
2012-03-12 18:50 ` Ulrich Mueller
2012-03-12 18:58 ` Ian Stakenvicius
2012-03-12 19:01 ` Ciaran McCreesh
2012-03-12 19:49 ` Ulrich Mueller
2012-03-12 20:10 ` Ciaran McCreesh
2012-03-12 20:21 ` James Broadhead
2012-03-12 21:14 ` Ulrich Mueller
2012-03-12 21:28 ` Kent Fredric
2012-03-12 21:49 ` Alec Warner
2012-03-12 22:02 ` Mike Gilbert
2012-03-12 22:37 ` Kent Fredric
2012-03-12 22:53 ` Alec Warner
2012-03-13 6:31 ` [gentoo-dev] " Duncan
2012-03-12 22:55 ` James Broadhead [this message]
2012-03-13 6:06 ` [gentoo-dev] " Ulrich Mueller
2012-03-12 22:06 ` James Broadhead
2012-03-12 22:17 ` Alec Warner
2012-03-12 19:00 ` Ciaran McCreesh
2012-03-12 19:38 ` Ulrich Mueller
2012-03-12 19:42 ` Ciaran McCreesh
2012-03-13 20:33 ` Brian Harring
2012-03-13 0:51 ` Patrick Lauer
2012-03-12 18:29 ` Kent Fredric
2012-03-13 4:31 ` Brian Harring
2012-03-13 5:14 ` Kent Fredric
2012-03-13 6:22 ` Brian Harring
2012-03-13 16:10 ` Wulf C. Krueger
2012-03-13 19:08 ` Brian Harring
2012-03-13 7:11 ` [gentoo-dev] " Duncan
2012-03-12 18:01 ` [gentoo-dev] " Michał Górny
2012-03-12 17:53 ` Ulrich Mueller
2012-03-12 18:03 ` Kent Fredric
2012-03-13 0:46 ` Patrick Lauer
2012-03-13 6:41 ` Walter Dnes
2012-03-13 6:56 ` Kent Fredric
2012-03-13 7:03 ` Brian Harring
2012-03-13 8:50 ` Ulrich Mueller
2012-03-13 15:52 ` Zac Medico
2012-03-13 7:30 ` Ciaran McCreesh
2012-03-14 0:29 ` Walter Dnes
2012-03-14 0:48 ` Michael Orlitzky
2012-03-14 1:42 ` Brian Harring
2012-03-14 2:05 ` Zac Medico
2012-03-14 2:23 ` Michael Orlitzky
2012-03-14 2:36 ` Zac Medico
2012-03-14 2:38 ` Michael Orlitzky
2012-03-14 2:38 ` Brian Harring
2012-03-14 2:47 ` Zac Medico
2012-03-12 16:56 ` Ulrich Mueller
2012-03-12 18:04 ` Michał Górny
2012-03-13 6:29 ` Richard Yao
2012-03-13 11:52 ` Rich Freeman
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='CA+hid6H=tGqtXzQOt2PYA8wD26a0OQNGN7sScZWP96px6Tae3w@mail.gmail.com' \
--to=jamesbroadhead@gmail.com \
--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