Ricardo Loureiro wrote:
Usable in the way that the client machines should be able to use portage, except it's the hacked (or new package) version that should do everything from the SQL server. For example, a emerge package would behave in 2 possible ways;1- calculate it's dependencies from the portage tree on the SQL server and request the binary packages, 2- Request the package and the server would calculate dependencies and get the binary done. I'm more keen on the second since it takes away processor time from the clients, but that involves sending sensitive information such as world files and make.conf over the network.
Sounds like in your setup you would like to keep a profile of the client on the server, so you don't have to send over that information, because it is already in the DBMS. That also allows you to update 'push-driven', because the server can easily tell which clients have packages that are out of date.
-- Fabian Groffen -- [email protected] mailing list
