Jens Deppe wrote: > > Shawn Walker wrote: >> Jens Deppe wrote: >>> >>> Shawn Walker wrote: >>>> Alok Aggarwal wrote: >>>>> On Wed, 26 Nov 2008, Jens Deppe wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Would it be reasonable to submit an RFE to have similar >>>>>> functionality as >>>>>> what post_install_repo_default_authority provides in the DC, in the AI >>>>>> as well? >>>>>> >>>>>> I don't believe the capability currently exists to be able to install >>>>>> from, say, a local repo, but then have the final installed system be >>>>>> setup to have it's default authority set to something else. >>>>> I think it is entirely reasonable to request >>>>> this functionality. >>>> I do as well, but be careful here. pkg(5) records what authority a >>>> package is installed from. While this should work, you will want to >>>> do extra verification. >>>> >>> By 'verification', I presume you mean whether this is even feasible, >>> as opposed to verification as part of the potential implementation? >> In other words, you'll want to be certain that the system still >> installs, updates, uninstalls, etc. as you expected with one more >> authorities configured and so forth. >> >> You should probably be cautious about what authority name you use since >> that will be recorded in files on the system and thus be visible to >> users that dig through the package files. >> > > I wasn't actually thinking about the authority name itself, but rather > the URL for that authority. My specific use case would be for a > manufacturing environment where I would need a local mirror of > pkg.opensolaris.org to install from because access to the 'real' > pkg.opensolaris.org is either too slow or non-existent. > > As far as pkg(5) permits, however, changing authorities should probably > also be possible.
It does allow for it, but I honestly don't know what side affects that will have when you get into a multiple authority situation, etc. -- Shawn Walker
