public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sérgio Almeida" <mephx.x@gmail.com>
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 20:42:58 +0100	[thread overview]
Message-ID: <1246304578.4316.92.camel@thedude> (raw)
In-Reply-To: <4A490FAC.6000105@hartwork.org>

[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]

Sebastian,

> 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.

I considered XML/JSON in this decision and did not even discussed it
with my mentor. This is indeed not and abandoned idea as I explain
below.

> 
> 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.
> 

I'm in no position to chose the path to take but for now python still
seems the chosen "vehicle". Remember that using XML/JSON for modules
would never need a re-write from uselect but would only be an extension
to the module system. Let us see.

In uselect everything are objects. 

Module is a class
Action is a class

Module(s) have Action(s)

Actions are interfaces to many kinds of actions, Sym, Path, Runnable

Sym and Path actions have Link(s)

Runnable actions have code and know how to execute it.

Therefore the backend scenario (object space) is the same as the new
suggested module syntax.

Basically this decision is not adding a feature. It is abandoning the
"uselect syntax" thus removing a feature.

This will help during development as parsing is the task that has been
more time consuming during uselect's development.

With this uselect will have an open interface for extension to any
markup language that comes in handy in module readability/programming.

> 
> Thanks for listening,
> 
> 
> 
> Sebastian
> 

I thank you. Will now add the markup language support to the to-do list,
not to implement right away but to have in mind while expanding the API.

Cheers,
Sérgio

-- 
Sérgio Almeida - mephx.x@gmail.com
mephx @ freenode


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-29 19:43 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   ` [gentoo-dev] Re: [gentoo-soc] " Sebastian Pipping
2009-06-29 19:42     ` Sérgio Almeida [this message]
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=1246304578.4316.92.camel@thedude \
    --to=mephx.x@gmail.com \
    --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