Bug 1179905 - [dnf] select default optional addons when changing environments
Summary: [dnf] select default optional addons when changing environments
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker
Depends On: 1179903
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-07 18:46 UTC by David Shea
Modified: 2015-01-27 16:50 UTC (History)
8 users (show)

Fixed In Version: anaconda-22.14-1
Clone Of:
Environment:
Last Closed: 2015-01-27 16:50:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Shea 2015-01-07 18:46:35 UTC
Description of problem:
Some optional groups for an environment are marked with default="true". When switching environments in the software spoke, these should be selected by default.

Currently in F22, the only two such groups are xfce-apps and xfce-media in xfce-desktop-environment.

Version-Release number of selected component (if applicable):
anaconda-22.13-1

Additional info:
Basically, implement environmentOptionIsDefault in dnfpayload once that's possible.

Comment 1 Fedora Blocker Bugs Application 2015-01-07 18:51:33 UTC
Proposed as a Blocker for 22-final by Fedora user dshea using the blocker tracking app because:

 The closest criterion I see is:

The installer must be able to use all supported local and remote package and installer sources. 

but maybe it should block earlier, I don't know.

Comment 2 David Shea 2015-01-08 14:44:01 UTC
Well that turned out to be less of a hassle than I expected.

Comment 3 Adam Williamson 2015-01-12 16:42:42 UTC
Discussed at 2015-01-12 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-12/f22-blocker-review.2015-01-12-16.06.log.txt . As none of the release-blocking package sets uses default optiongroups, we didn't feel this actually meets any of the release criteria. If any of the release-blocking package sets *did* use that feature this would be an Alpha or Beta blocker. We can revisit for FE status if necessary or for blocker status if one of the release-blocking package sets starts using this feature, but for now we simply rejected the bug as a blocker (of course, the fix is still welcome!)


Note You need to log in before you can comment on or make changes to this bug.