So this makes the offline repository virtually unusable for SPARC until the elusive SPARC boot image arrives.
Surely you are not going to change the repository format with every build? I can understand upgrading it occasionally, but without the option to upgrade the pkg software separately this makes it impossible for disconnected sites to be able to upgrade without doing a re-install for each version (if they have x86) since the iso images don't support upgrades. And until the SPARC iso arrives it is totally impossible if they only have SPARC installation. Having a requirement to do a re-install of the OS every time you want to serve a new repository is not really an acceptable scenario. We need something for the pkg tools like the current situation with the lu packages on Solaris, where you can add the latest lu packages to an existing OS so you can upgrade to a new version. Cheers Frank Shawn Walker wrote: > Frank Allan wrote: >> Is it a requirement for the OS build to be equal or greater than the >> repo it >> hosts, or is there something else happening? I am sure I would have seen > > Not the OS build, but the depot software in question has to match the > OS build. You can use new package software with old repositories or > OS builds, but not the other way around. > > You can't use depot software from any build before 127 with a > repository for build 127. > > Cheers,
