public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Are tags just sets?
Date: Mon, 27 Jun 2011 00:17:44 +1200	[thread overview]
Message-ID: <BANLkTi=bheepJXpLV-fn-kQJ_xkMYo7oTQ@mail.gmail.com> (raw)
In-Reply-To: <20110626080257.12d523ef@googlemail.com>

On 26 June 2011 19:02, Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> Here's a completely different way of doing tags:
>
> First, standardise sets. We probably want to go with a format along the
> lines of:
>
>    eapi = 4
>    description = Monkeys
>
>    dev-monkey/howler
>    dev-monkey/spider
>    >=dev-monkey/spanky-2.0
>    dev-monkey/squirrel
>
> where eapi has to be on the first line.
>

I initially didn't like the idea somewhat, but then I figured the
amount of impact and retooling required to make this work is virtually
zero, its not complicated, and its text based.

So why don't we just implement it, even if it sucks balls, the amount
of downsides it has are zero really, it doesn't affect how portage
currently works at all, so if we prove it to suck or decide it needs
replacing, we can throw it out and put something else in with very
little pain.

So +1.

( Yes, I understand the concerns of Yet Another format, I myself would
suggest JSON for a plethora of reasons were it up to me, and all
though it is /mostly/ just a list of package specs, those "first
lines" with the = in them make this more "format" than just a text
file, but I think we should see whether or not the concept works FIRST
before debating whether or not we've bikeshedded the right format to
put it in ).


-- 
Kent

perl -e  "print substr( \"edrgmaM  SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"

http://kent-fredric.fox.geek.nz



  parent reply	other threads:[~2011-06-26 12:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-26  7:02 [gentoo-dev] Are tags just sets? Ciaran McCreesh
2011-06-26  8:41 ` Michał Górny
2011-06-26  8:43   ` Ciaran McCreesh
2011-06-26  8:54     ` Michał Górny
2011-06-26  9:00       ` Ciaran McCreesh
2011-06-26 12:48         ` Michał Górny
2011-06-27  5:51           ` Ciaran McCreesh
2011-06-26 11:33 ` Wyatt Epp
2011-06-26 12:17 ` Kent Fredric [this message]
2011-06-26 14:40 ` [gentoo-dev] " Duncan
2011-06-26 15:12 ` [gentoo-dev] " Maciej Mrozowski
2011-06-26 18:42   ` Kent Fredric
2011-06-27  5:49   ` Ciaran McCreesh
2011-06-27 18:21     ` Maciej Mrozowski
2011-06-28  6:19       ` Ciaran McCreesh
2011-06-27 20:23     ` Rich Freeman
2011-06-27 21:06       ` Wyatt Epp
2011-06-27 21:23         ` Rich Freeman
2011-06-27 21:39           ` Wyatt Epp
2011-06-28  6:19       ` Ciaran McCreesh
2011-06-28  3:26 ` Brian Harring
2011-06-28  3:43   ` Kent Fredric
2011-06-28  9:31     ` Brian Harring
2011-06-28 11:53   ` Peter Volkov
2011-06-28 15:33     ` Wyatt Epp
2011-06-28 18:52   ` Maciej Mrozowski

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='BANLkTi=bheepJXpLV-fn-kQJ_xkMYo7oTQ@mail.gmail.com' \
    --to=kentfredric@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