Bug 1080108 - Drop openSUSE-release-mini
Drop openSUSE-release-mini
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Current
Other Other
: P3 - Medium : Enhancement (vote)
: ---
Assigned To: Dominique Leuenberger
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-08 16:30 UTC by Fabian Vogt
Modified: 2018-06-14 11:49 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Vogt 2018-02-08 16:30:52 UTC
openSUSE-release-mini is used in build environments to provide product_flavor.

I don't see any reason to offer it as openSUSE-release-ftp is the same for all intents and purposes.

As it's never been published in the repos, it should be safe to remove by just replacing "mini" with "ftp" in openSUSE.product
Comment 1 Dominique Leuenberger 2018-02-08 16:54:27 UTC
Adrian,

Can you please give me a crash course about the meaning of that 'flavor' setting in the product and into what traps I will step by changing them?
Comment 2 Adrian Schröter 2018-02-09 07:57:03 UTC
The main purpose of flavors these days is to identify the way of installation for statistics. The default is _not_ to create flavor packages when using product-builder anymore, but I was told that it is still wanted for openSUSE for the statistics. So there is still an option to enable flavors.

-mini is not used in build environments by default. It may be used as workaround to identify non-official builds for appliances.

The original purpose of it was to identify network installations.

I would not touch the flavors with old kiwi builder since it has some more consequences, but IMHO out of scope here.
Comment 3 Dominique Leuenberger 2018-02-09 08:00:25 UTC
(In reply to Adrian Schröter from comment #2)
> 
> The original purpose of it was to identify network installations.
> 
> I would not touch the flavors with old kiwi builder since it has some more
> consequences, but IMHO out of scope here.

Ok, following this advise, I will wait for the migration to the new prod builder and then eliminate the flavors.
Comment 4 Ludwig Nussel 2018-06-14 11:49:11 UTC
I'd really like to have some insights in deployment methods in the future so we actually see if people start with an installation or applicance. So instead of eliminating flavors I'd like to see some that help us to identify eg JeOS and docker images.