public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EBUILD_FORMAT support
Date: Thu, 07 Jul 2005 08:19:49 -0400	[thread overview]
Message-ID: <1120738789.1972.0.camel@localhost> (raw)
In-Reply-To: <200507070047.35274.vapier@gentoo.org>

On Thu, 2005-07-07 at 00:47 -0400, Mike Frysinger wrote:
> On Thursday 07 July 2005 12:36 am, Kito wrote:
> > On Jul 6, 2005, at 8:01 PM, Nathan L. Adams wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Sven Wegener wrote:
> > >> On Wed, Jul 06, 2005 at 08:41:43PM -0400, Mike Frysinger wrote:
> > >>> On Wednesday 06 July 2005 08:20 pm, Sven Wegener wrote:
> > >>>> We would like to introduce a new ebuild variable named
> > >>>> EBUILD_FORMAT,
> > >>>
> > >>> seems like the name is much longer than it needs to be ... what's
> > >>> wrong with
> > >>> say 'EVER' ?
> > >>
> > >> It's fine too. EBUILD_FORMAT was just the name that fell in
> > >> #gentoo-portage once we discussed about it.
> > >>
> > >> Sven
> > >
> > > EVER looks like the english word 'ever'; what does it stand for?
> > > EBUILD
> > > VERSION? If so, how about EVERSION? Since when was variable name
> > > length
> > > a problem? Go with whatever best describes the variable and is easy to
> > > figure out.
> >
> > Why not follow that logic through and use something like EBUILD_API ?
> > the term VERSION implies release version which of course may not be
> > tied to API changes...
> 
> hmm that sounds even better ... EAPI ?

I would be in favor of EAPI= or an even shorter variable name.

strlen(EBUILD_FORMAT) * 19546 = 249K
strlen(EAPI) * 19546 = 77K
strlen(EV) *  19546 = 39K

Where 19546 is the number if ebuilds in the tree as.

-- 
Ned Ludd <solar@gentoo.org>

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-07-07 12:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  0:20 [gentoo-dev] EBUILD_FORMAT support Sven Wegener
2005-07-07  0:41 ` Mike Frysinger
2005-07-07  0:49   ` Sven Wegener
2005-07-07  1:01     ` Nathan L. Adams
2005-07-07  1:09       ` Sven Wegener
2005-07-07  1:22         ` Olivier Crête
2005-07-07  1:28         ` Joshua Baergen
2005-07-07  4:36       ` Kito
2005-07-07  4:47         ` Mike Frysinger
2005-07-07 12:19           ` Ned Ludd [this message]
2005-07-07 12:31             ` Diego 'Flameeyes' Pettenò
2005-07-07 14:37             ` twofourtysix
2005-07-07 17:20               ` Alec Warner
2005-07-07 17:52             ` Donnie Berkholz
2005-07-07 18:28               ` Maurice van der Pot
2005-07-08  3:31                 ` Donnie Berkholz
2005-07-07 20:42               ` Robin H. Johnson
2005-08-23 13:20                 ` Paul de Vrieze
2005-08-23 16:00                   ` Brian Harring
2005-08-25 10:34                     ` Paul de Vrieze
2005-08-26  7:35                       ` Brian Harring
2005-08-26 11:19                         ` [gentoo-portage-dev] " Paul de Vrieze
2005-08-26 12:50                           ` Paul de Vrieze
2005-08-26 14:58                             ` Ciaran McCreesh
2005-08-26 15:08                               ` Paul de Vrieze
2005-08-26 15:11                               ` Paul de Vrieze
2005-08-26 15:20                                 ` Paul de Vrieze

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=1120738789.1972.0.camel@localhost \
    --to=solar@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