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 via email to