From Fedora Project Wiki
Line 8: Line 8:
 
# '''install time''' -- we want the product you're installing to determine which configuration you get.
 
# '''install time''' -- we want the product you're installing to determine which configuration you get.
 
# '''installing a package on an existing system''' -- if it has separate config, we'd like the package manager to choose the configuration for the product you're using.
 
# '''installing a package on an existing system''' -- if it has separate config, we'd like the package manager to choose the configuration for the product you're using.
 +
# Want to have a single tool that can switch default configs per-package.  Which things you can switch may depend on what combinations we support and how the user has selected which Products are "active" on their system.
  
 
=== Discussing ===
 
=== Discussing ===
Line 13: Line 14:
 
# Product conversion/union: Installed Cloud or Server but want a graphical environment. Preference is to make that be Workstation.  (We want it to be as close to Workstation as possible, to benefit from existing testing)
 
# Product conversion/union: Installed Cloud or Server but want a graphical environment. Preference is to make that be Workstation.  (We want it to be as close to Workstation as possible, to benefit from existing testing)
 
## recommendation implementation: the defaults should not change for anything that was part of the installed Product, but new packages should get the Workstation default
 
## recommendation implementation: the defaults should not change for anything that was part of the installed Product, but new packages should get the Workstation default
# If we have a union Product (e.g. Server+Workstation), a nice-to-have would be a single tool to adjust all configs for one or the other.
 
  
 
== Possible Implementations ==
 
== Possible Implementations ==

Revision as of 18:41, 7 March 2014

We want to have products be able to specify divergent and conflicting behaviour.

Use cases

Agreed upon

(at least sgallagh and abadger1999 :-)

  1. install time -- we want the product you're installing to determine which configuration you get.
  2. installing a package on an existing system -- if it has separate config, we'd like the package manager to choose the configuration for the product you're using.
  3. Want to have a single tool that can switch default configs per-package. Which things you can switch may depend on what combinations we support and how the user has selected which Products are "active" on their system.

Discussing

  1. Product conversion/union: Installed Cloud or Server but want a graphical environment. Preference is to make that be Workstation. (We want it to be as close to Workstation as possible, to benefit from existing testing)
    1. recommendation implementation: the defaults should not change for anything that was part of the installed Product, but new packages should get the Workstation default

Possible Implementations

  • Conflicts
  • Alternatives