Would this process involve listening on a network or local port? In other words, is the depot server started a general purpose server, or is it in some fashion tied tightly to the requester (like talking via a pipe instead of a TCP connection)?
Opening up a listening socket, even a local one, is security-impolite. It also sounds kind of inefficient, moving all those bytes through an "extra" process and some kind of IPC. Shawn Walker wrote: > Greetings, > > After working on the depot code lately, one of the things that I've > been thinking about is enabling easier local installation. > > Specifically, if a user can point us at a directory that contains a > valid repository, or at a tarball that contains a valid repository, we > could let the pkg client start a depot server child process and > perform the authority magic and everything else needed to install the > package from it. > > I know you have all been discussing this for some time already, but I > thought I would re-start this discussion as its something I'd like to > work on soon. > > I've been hacking on a prototype of this that modifies client.py by: > > * adding a global -d repo_dir parameter > > * doesn't allow it to be specified in combination with the authority > subcommands > > * Grabs the current authority for the image > > * Uses depotcontroller to start a local depot server using the value > of -d as the depot root > > * Sets the new authority to the URL of the newly started depot server > > * Proceeds with the actual subcommand they specified > > * Regardless of success resets the authority to what it was originally > > I was wondering if this was the approach that some of you were > thinking about using to deal with "repository on disk as a package". > > Cheers, _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
