Re: [gentoo-dev] new guides

[Tom Flavel <thomasfl@cogs.susx.ac.uk>]

On Fri, Apr 13, 2001 at 11:38:28AM +0200, Achim Gottinger wrote:
> 
> We had a discussion about allowing other languages like perl or tcl/tk
> to be used for ebuild. And decided that
> it makes more sense converting stable parts of python code to c++. Once
> it's all c++ we can make modules
> for other scripting languages. I personal prefer perl as a scripting
> language and did not investigate much
> time in learning python. But as long as daniel is the developer of
> ebuild it is his right do choose his
> preferend language for development I think.
> Our biggest problem is still that we can not spend all our time in
> gentoo development as long as we do not have
> sponsors.
> 
> There is a install-gui in development that will use qt first, but it
> will be designed in a manner that the gui
> parts are separated from the configuration backend, so it should be easy
> to write ncurses or gtk frontends too.
> But do not expect that stuff next week. :-)
> 

Hi,

on a similar note, I remember discussing seperating the backend of portage
from interfaces a while ago, but I think it may have been a bit too early :)

To recap, the idea was to have a C/C++ program listen on a pipe, then have
interfaces (in the language of your choice) do things like
"echo packagename>/thatpipe" - the backend would listen and install the package.

This would mean one could churn out gui's using the wigit tool of personal
prefence, for example, with relative ease. A bouns is that as the protocol
would be simple (basically just a package name/version and what to do with it)
the actual behaviour would be consistent across all interfaces.

- Tom