public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luis Francisco Araujo <araujo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion
Date: Thu, 08 Feb 2007 10:42:44 -0400	[thread overview]
Message-ID: <45CB36E4.30001@gentoo.org> (raw)
In-Reply-To: <1170938355.26065.12.camel@vertigo.twi-31o2.org>

Chris Gianelloni wrote:
> On Thu, 2007-02-08 at 11:59 +0100, Jose San Leandro wrote:
>> That is enough once you know how to write ebuilds.
>>
>> We were thinking of a GUI to soften the learning curve to non-experts. 
>> Probably not useful for a Gentoo developer, but could provide an easy way to 
>> write ebuilds to project maintainers themselves, not to Gentoo resources.
> 
> I think what everyone means here is that if the default functions don't
> cover it, and an eclass doesn't cover it, then all of the code will have
> to be written by hand, anyway.  No amount of pretty clicky interfaces
> will help this.
> 
> The only thing I would really see as being useful would be a simple help
> system that is aware of all of the functions in ebuilds.  This could be
> possible if there were some standardized way to document functions and
> their uses, so it could be parsed at run-time from the tree itself, but
> currently, I don't see it getting much traction.  Don't get me wrong, I
> see lots of places where work could be done to make things easier, such
> as some way to easily determine dependencies.  I just don't think it is
> possible to write up an IDE until more work is done defining the current
> eclasses and functions into something more static.
> 

It'd be very difficult to replace just 'opening a text editor' by an 
IDE. Though you might probably come up with very cool ideas ; like for 
example, an eclass browser that could search function based on name or 
descriptions of what the developer is looking for; probably with some 
hierarchy view for surfing them.

At the end, i guess a text editor would be the best option; but that 
doesn't mean you can't try new methods/ideas.

Regards,

-- 

Luis F. Araujo "araujo at gentoo.org"
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-02-08 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  9:38 [gentoo-dev] Suggestion Jose San Leandro
2007-02-08  9:43 ` Ciaran McCreesh
2007-02-08 10:50   ` Christopher Covington
2007-02-08 13:26     ` Joshua Nichols
2007-02-14 10:40     ` [gentoo-dev] Suggestion Steve Long
2007-02-08 10:59   ` [gentoo-dev] Suggestion Jose San Leandro
2007-02-08 12:39     ` Chris Gianelloni
2007-02-08 14:42       ` Luis Francisco Araujo [this message]
2007-02-08 10:40 ` Alistair Bush
  -- strict thread matches above, loose matches on Subject: below --
2002-06-19 16:44 [gentoo-dev] suggestion Andy Molloy

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=45CB36E4.30001@gentoo.org \
    --to=araujo@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