* Stephen Hahn <sch at sun.com> [2007-10-02 22:03]:
> * Peter Tribble <peter.tribble at gmail.com> [2007-09-30 21:16]:
> > While there exists an OpenSolaris install strategy, that strategy
> > explicitly does not encompass packaging and patching, for which a
> > separate strategy is needed.
> > 
> > Development of such a strategy is sorely needed. Especially given
> > current concerns over where packaging is headed. We should be asking:
> > 
> >  - What are the future needs that the package/patch system needs to
> > address?
> > 
> >  - What are the shortcomings of the current system?
> > 
> >  - What steps need to be taken to fix the current problems and address
> > future needs?
 
  So, the relevant Indiana requirements, as they coalesced, are also
  useful, because there was a public negotiation around them as well, so
  we can assume that the text was debated to some level of acceptance.
  The ones I pick out from

  http://opensolaris.org/os/project/indiana/documents/problem_statement/

  are

  INS-2: Existing installations should allow a seamless upgrade to the
         next consecutive stable release or future releases within
         certain well defined boundaries.

  PKG-1: Provide package management infrastructure that allows easy
         install, configuration and removal of software with full
         dependency checking and a 'just works' experience.

  PKG-2: Software will either be installed by default on a single CD, or
         easily available over the network in binary form through package
         management tools.

  PKG-3: Software should also be available in meta clusters for people
         to install specific to their needs eg.  Web 2.0 meta cluster.

  PKG-4: An existing network repository can be easily mirrored, and
         users can appropriately configure their system to install
         packages from there instead.

  PKG-5: Provide a series of tools to allow developers to create and
         maintain their own set of packages as part of an unsupported
         package repository, or propose them for a supported package
         repository.

  PKG-6: Packages will be upgraded as appropriate through an automatic
         update facility and notification to the user.

  PKG-7: It should be possible to preserve the current environment prior
         to an update so that a rollback is possible in case of
         breakages.

  - Stephen
  
--  
sch at sun.com  http://blogs.sun.com/sch/

Reply via email to