public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-soc@lists.gentoo.org
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-soc] Re: Progress on Universal Select Tool
Date: Mon, 29 Jun 2009 21:02:04 +0200	[thread overview]
Message-ID: <4A490FAC.6000105@hartwork.org> (raw)
In-Reply-To: <1246301448.4316.68.camel@thedude>

Sérgio Almeida wrote:
> user action bin {
> 	description "Change Python's Version"
> 	type sym
> 	sym python {
> 		bin python
> 		target /usr/bin/python 
> 		prefix /usr/bin/ 
> 		regexp python([0-9]+\.[0-9]+$)
> 		sym python-config {
> 			bin python-config
> 			destination /usr/bin/python-config
> 			prefix /usr/bin/ 
> 			regexp python([0-9]+\.[0-9]+)-config($)
> 		} python-config
> 	} python
> } bin
> 
> Soon urged the need for more complex lexical analysis and started
> implementing lex rules and yacc skeleton.
> 
> With this step a question bounced into my head. 
> 
> Am I reinventing the wheel? 
> Why implement lex/yacc to translate a block of code into a python's
> block of code?
> Why not use plain python in modules?
> 
> After discussing with mentor, we decided to adopt python as the base
> language for uselect modules.

It seems to me that the original langauge is "static"/"descriptive"
while Python is not.  Why not move to XML or JSON (former seems more
common with Gentoo) instead of Python?  Think about how much easier it
is to pull information from metadata.xml than from .ebuild files - it's
the same difference in your case.

You know much better where you want to go with this than I do, but
please triple-check this move, as you cannot go back.

Thanks for listening,



Sebastian



  reply	other threads:[~2009-06-29 19:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 14:48 [gentoo-dev] Progress on Universal Select Tool Sérgio Almeida
2009-06-17 18:32 ` [gentoo-dev] " Sérgio Almeida
2009-06-29 18:50 ` Sérgio Almeida
2009-06-29 19:02   ` Sebastian Pipping [this message]
2009-06-29 19:42     ` [gentoo-dev] Re: [gentoo-soc] " Sérgio Almeida
2009-07-13 15:36 ` [gentoo-dev] " Sérgio Almeida
2009-07-14  9:20   ` Michael Haubenwallner
2009-07-15 15:42     ` Sérgio Almeida
     [not found]     ` <1247582117.3651.3.camel@thedude>
     [not found]       ` <1247584057.14345.29.camel@sapc154.salomon.at>
2009-07-15 15:43         ` Sérgio Almeida
2009-07-16  6:22           ` Michael Haubenwallner
2009-07-22 18:41 ` Sérgio Almeida
2009-07-23  3:09   ` [gentoo-dev] Re: [gentoo-soc] " Nirbheek Chauhan
2009-07-23  4:43     ` Sérgio Almeida
2009-07-23  5:32       ` Nirbheek Chauhan
2009-07-23 13:35         ` Sérgio Almeida
2009-07-23 15:28           ` Robert Buchholz
2009-07-23 18:33             ` Sérgio Almeida
2009-07-24  8:22               ` Michael Haubenwallner
2009-07-24 15:20                 ` Sérgio Almeida
2009-07-27  8:33                   ` Michael Haubenwallner
2009-07-27 18:35                     ` Sérgio Almeida
     [not found]         ` <6f8b45100907230047k44111c77ha1b68e61b8c88bf2@mail.gmail.com>
2009-07-23 13:40           ` Sérgio Almeida
2009-07-23  6:12     ` [gentoo-dev] " Duncan
2009-08-01 18:46 ` Sérgio Almeida
2009-08-18 15:23 ` Sérgio Almeida

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=4A490FAC.6000105@hartwork.org \
    --to=webmaster@hartwork.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-soc@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