[EMAIL PROTECTED] wrote: >> I wasn't aware that pkg.client was considered the exclusive domain of >> the cli given that much of it's code is shared. > > Last time I checked, client.py was the CLI. Did you mean you wanted the > code to live somewhere in modules/client?
Yes, as in the pkg.client module (e.g. "import pkg.client") :) >> If your concern is about crossing boundaries, then it should be put into >> the API. > > I'm not sure these environment variables need to be exposed to the front > ends through an API. It would make more sense to have > socket.defaulttimeout and max_timeouts live behind the API for the front > ends. The fact that they're currently exposed is a historical artifact > of our ad-hoc development process, not an indication of overall design > goals. Ah, I had thought it was intentional that we exposed them. In that case, I'd agree with your sentiment of putting them into new, public client API Brock wrote. >> misc doesn't seem like the right place for something that has a central >> effect on the client -- that was what I was trying to communicate. > > It's not clear to me that we have a better place for miscellaneous > global state, at least for now. ...our dumping ground grows ever larger :) -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
