Skip to content

Make the user visible patterns configurable, added MicroOS products#916

Merged
lslezak merged 15 commits intomasterfrom
user_patterns
Dec 6, 2023
Merged

Make the user visible patterns configurable, added MicroOS products#916
lslezak merged 15 commits intomasterfrom
user_patterns

Conversation

@lslezak
Copy link
Contributor

@lslezak lslezak commented Dec 5, 2023

Problem

Solution

  • Do not display all available patterns in the pattern selector, display only the explicitly listed patterns configured in the product YAML file

Additional Fixes

  • The Leap 16.0 product has been removed (discussed with Luboš)
  • Added new openSUSE MicroOS products
  • Enhanced the yupdate code to also patch the product definitions

Testing

  • Added new unit tests
  • Tested manually

Screenshots

openSUSE Tumbleweed openSUSE MicroOS
tw-patterns microos-patterns
openSUSE MicroOS Desktop Product Selection
microdesktop-patterns product-selection

@coveralls
Copy link

coveralls commented Dec 5, 2023

Coverage Status

coverage: 75.044% (+0.05%) from 74.998%
when pulling 97da667 on user_patterns
into 2c46c58 on master.

FileUtils.mkdir_p(File.dirname(target))
FileUtils.cp(f, target)
else
# if there is a new product file it needs to be copied manually
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without putting too much thinking into it... not sure if this is the behavior I would expect.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well, problem is that it is hard to know which product belongs to which iso

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that the Git repository contains YAML files for all product. If you are patching the openSUSE Agama installer then the Live medium contains only the openSUSE products.

If yupdate would install all files you would suddenly see the ALP Dolomite product in the list, that would be confusing. So I decided to patch only the existing files and to not blindly copy everything available. IMHO it is better to have a safer default behavior.

- gnome
- yast2_basis
- yast2_desktop
- yast2_server
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if it makes sense to have all three. Maybe just desktop and server yast modules will be enough?

Copy link
Contributor Author

@lslezak lslezak Dec 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure. If you want to have YaST just for the package management then the yast2_basis is enough. On the other hand the yast_desktop pattern adds just few megabytes more, not a big deal...

Copy link
Contributor

@jreidinger jreidinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, nothing critical

@lslezak lslezak merged commit 3953469 into master Dec 6, 2023
@lslezak lslezak deleted the user_patterns branch December 6, 2023 09:32
@imobachgs imobachgs mentioned this pull request Dec 21, 2023
imobachgs added a commit that referenced this pull request Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants