James C. McPherson wrote:
> > > The only workaround I can think of for now is to setup a nwam
> > > network profile and then have a script that changes the pkg
> > > publisher configuration when the network profile is activated.
> >
> > Thanks for the replies. The hack I've been using is to point each
> > publisher to localhost:someport and then redirect that port to
> > ipkg or my local repo depending on what network I'm on. The nwam
> > script is probably a bit prettier. :^)
>
> Hi Stephen, Do you have a script to set up this redirection, or are
> you doing it by hand? I'm interested in how you're doing it.
Hi James,
Nothing terribly complex:
# When on OWAN
% ssh -L 10080:ipkg.us.oracle.com:80 <any_oracle_host>
# When on local LAN
% ssh -L 10080:nerd:80 <any_lan_host>
(nerd is the host on my LAN with an s11u repo.)
Now all the ipkg repos are reachable:
% pkg publisher
PUBLISHER URI
...
solaris http://localhost:10080/solaris11/dev/
internal-only http://localhost:10080/internal/solaris11/internal-only/
solarisstudio http://localhost:10080/solarisstudio/release/
I haven't automated it, mostly because I don't generally need anything
from the pkg system. But when I do, it's a quick hack that gets the
job done.
Steve
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
