| 1 |
On Fri, Apr 13, 2001 at 11:38:28AM +0200, Achim Gottinger wrote: |
| 2 |
> |
| 3 |
> We had a discussion about allowing other languages like perl or tcl/tk |
| 4 |
> to be used for ebuild. And decided that |
| 5 |
> it makes more sense converting stable parts of python code to c++. Once |
| 6 |
> it's all c++ we can make modules |
| 7 |
> for other scripting languages. I personal prefer perl as a scripting |
| 8 |
> language and did not investigate much |
| 9 |
> time in learning python. But as long as daniel is the developer of |
| 10 |
> ebuild it is his right do choose his |
| 11 |
> preferend language for development I think. |
| 12 |
> Our biggest problem is still that we can not spend all our time in |
| 13 |
> gentoo development as long as we do not have |
| 14 |
> sponsors. |
| 15 |
> |
| 16 |
> There is a install-gui in development that will use qt first, but it |
| 17 |
> will be designed in a manner that the gui |
| 18 |
> parts are separated from the configuration backend, so it should be easy |
| 19 |
> to write ncurses or gtk frontends too. |
| 20 |
> But do not expect that stuff next week. :-) |
| 21 |
> |
| 22 |
|
| 23 |
Hi, |
| 24 |
|
| 25 |
on a similar note, I remember discussing seperating the backend of portage |
| 26 |
from interfaces a while ago, but I think it may have been a bit too early :) |
| 27 |
|
| 28 |
To recap, the idea was to have a C/C++ program listen on a pipe, then have |
| 29 |
interfaces (in the language of your choice) do things like |
| 30 |
"echo packagename>/thatpipe" - the backend would listen and install the package. |
| 31 |
|
| 32 |
This would mean one could churn out gui's using the wigit tool of personal |
| 33 |
prefence, for example, with relative ease. A bouns is that as the protocol |
| 34 |
would be simple (basically just a package name/version and what to do with it) |
| 35 |
the actual behaviour would be consistent across all interfaces. |
| 36 |
|
| 37 |
- Tom |
Archives