Hi Folks,

I'm looking for some best practice guidelines here. If we maintain a mirror of the Solaris 11 repository, we typically pull over the latest build of the S11 repo. How best should we manage clients running older builds which are not available on the mirror? For example, if my client is at b169 and my mirror was created with b172, and I try to install a package, I've seen errors like:


Reject: pkg://solaris/library/java/[email protected],5.11-0.172:20110816T143014Z
   Reason:  This version is excluded by installed incorporation
pkg://solaris/consolidation/dbtg/[email protected],5.11-0.169:20110705T151743Z


Some options are:

- dont support older builds; require clients to pkg update to the latest build on the mirror first. But possibly customers may not want to do this if they have standardized on a specific version.

- require the mirror to maintain  older content. e.g.

pkgrecv -s http://ipkg.us.oracle.com/solaris11/dev -d <myrepo> '*@0.5.11,5.11-0.169'
   (BTW, is this the correct command?)

Depending on the frequency of S11 updates, this could start consuming lots of space on the mirror to maintain older content.


Any suggestions would be greatly appreciated.

Thanks,

--shri







_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to