Gentoo Archives: gentoo-dev

From: Daniel Robbins <drobbins@g.o>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] new guides
Date: Fri, 13 Apr 2001 09:20:03
In Reply to: Re: [gentoo-dev] new guides by Tom Flavel
1 On Fri, Apr 13, 2001 at 01:05:55PM +0100, Tom Flavel wrote:
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.
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.
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.
17 Best Regards,
19 --
20 Daniel Robbins <drobbins@g.o>
21 President/CEO
22 Gentoo Technologies, Inc.


Subject Author
Re: [gentoo-dev] new guides Pete Gavin <pete@g.o>