On Mon, 2021-06-21 at 13:34 +0200, Adrian Schröter wrote:
Hi,
I like to discuss the upcomming single common name for repositories for "Code 15-3".
Given that we use the Jump concept now with Leap 15.3, it makes no sense that we offer by default
SUSE_SLE_15_SP3 SLE_15_SP3_Backports openSUSE_Leap_15.3
repositories in parallel for each OBS project anymore. The content should be identical and it contradicts the purpose of having a binary compatible base.
So, in near future OBS will change it's interface and allow basically only to select one repository for "Code 15-3". You can decide to include Backports or Leap packages on top of SLE 15 SP3 as build and install dependencies, but no matter how you configure it as OBS user, the resulting repository name should have the same name.
The big question is, what should this repository name be?
People need to understand that they can use it on openSUSE Leap 15.3 or on any SUSE SLE 15 SP3 installation.
Do you have any suggestions?
thanks adrian
I think the most 'correct' suggestion would be to use the term that both SUSE and openSUSE have used for quite some time to describe what we're doing in this area "Common Code Base" So something like "CCB_153" or "CCB_15.3" would be valid shortnames This avoids the problematic trademark/product issues - we can't call something SLE when it isn't SLE, we cant call something openSUSE when it isn't openSUSE, but you need something for the shared whole. Variations with "*SUSE" or "allSUSE" might be a valid option also, to reflect it's applicability to both the commercial and community SUSE SLE/openSUSE entities. "allSUSE_15.3" has a certain ring to it for me I have some more fun suggestions including "Monolith" or "SLElephant" but I was trying to keep things sensible :) Regardsm -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer