| 1 |
On Fri, Apr 13, 2001 at 01:05:55PM +0100, Tom Flavel wrote: |
| 2 |
|
| 3 |
> To recap, the idea was to have a C/C++ program listen on a pipe, then have |
| 4 |
> interfaces (in the language of your choice) do things like |
| 5 |
> "echo packagename>/thatpipe" - the backend would listen and install the package. |
| 6 |
|
| 7 |
One problem with this solution is that we need a robust and feature-rich two-way |
| 8 |
communications stream. For example, your request to install "foo/bar-1.0" may be |
| 9 |
answered by a list of dependencies that must be satisfied before installation is |
| 10 |
possible, or a particular dependency that couldn't be satisfied (if it's auto-resolving |
| 11 |
dependencies), or that the particular package wasn't found in the portage database. |
| 12 |
|
| 13 |
With such a system as you describe, the Portage response would have to be placed |
| 14 |
in another file, and tying these two files into a communications stream would become |
| 15 |
tricky enough to make this a less-than-elegant, solution. IMO. |
| 16 |
|
| 17 |
Best Regards, |
| 18 |
|
| 19 |
-- |
| 20 |
Daniel Robbins <drobbins@g.o> |
| 21 |
President/CEO http://www.gentoo.org |
| 22 |
Gentoo Technologies, Inc. |
Archives