On Fri, 14 Nov 2008, Alok Aggarwal wrote: > > On Fri, 14 Nov 2008, Alok Aggarwal wrote: > >> >> On Fri, 14 Nov 2008, Jens Deppe wrote: >> >>> Hello, >>> >>> I recently submitted bug 4487 which addresses the inability to use http >>> proxies with the auto installer: >>> >>> http://defect.opensolaris.org/bz/show_bug.cgi?id=4487 >>> >>> I'd like to pick this up and do the work for this RFE. It looks fairly >>> straight forward. >> >> It should be quite straight forward. >> >>> The approach I was thinking to take is to add the proxy value into the >>> manifest, as in: >>> >>> <ai_manifest name="default"> >>> <ai_pkg_repo_default_authority> >>> <main url="http://pkg.opensolaris.org"; >>> authname="opensolaris.org"/> >>> <mirror url=""/> >>> <proxy>http://10.1.149.91:8080</proxy> >> >> I'd change the proxy tag to be - >> >> <proxy url="http://10.1.149.91:8080"/> > > Actually thinking about this a little more, it is > quite concievable to have a user set different > proxies for different authorities/mirrors. Thus, the following > may be more desirable - > > <ai_manifest name="default"> > <ai_pkg_repo_default_authority> > <main url="http://pkg.opensolaris.org"; > authname="opensolaris.org" proxy="http://10.1.149.91:8080"/> > <mirror url="" proxy="http://172.2.2.5:8080";> > ..
Thinking about it even more, it occurs to me that pkg(1) doesn't allow this level of control. So, a single proxy specification at the top level like Dave says is what is best for now. Alok
