-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/27/2015 01:47 PM, Richard Brown wrote:
On 27 May 2015 at 19:28, Robert Schweikert
wrote: For :42 one has to create extra requests, one has to be prepared to support packages longer, and if newer versions of core packages are needed than those that come with "free maintenance" from SUSE one has to enter into negotiations with the maintainer of that package to override the package that comes from SLE.
Where does this come from?
Just thinking through the issues people mentioned.
Who said that in order for a newer version of a package to end up in openSUSE it will be required that an openSUSE contributor will need to 'enter into negotiations' with the SLE package maintainer?
Well, Christian maintains AppArmor and as he pointed out the version in SLE is a bit behind. Thus, there are two options, the openSUSE based on SLE releases uses the "free maintained by SUSE" antiquated version of AppArmor or it get overridden by the package from Factory. And I did not say that the maintainer of the package has to negotiate with the SLE maintainer. One has to negotiate with the maintainer of a newer package one depends on. Which are two different things. Simple example. Before the fully automated maintenance of Perl modules I maintained perl-Readonly. For a while I deliberately held the version of the package back to keep it building and working on SLES 11 SP3. Now with the automated maintenance and because Readonly was getting quite long in the tooth we have the latest version in OBS. However, it no longer builds and works on SLES 11 SP3. Thus, if we had an openSUSE version based on SLES 11 SP3 sources I would have to negotiate with the Perl maintainer to update Perl in that version of openSUSE if in the next .x release the Perl version would not increase and a new version of perl-Readonly is desirable for our users. Yes, I know the counter argument is, "you are talking about something old". Well, SLE 12 will be old in just a few years and we will still be stuck with those sources as the base for openSUSE.
Sure, I hope that this whole exercise leads to more openSUSE contributors talking to more SLE engineers and visa versa, but I think you're grossly misrepresenting the nature of that collaboration with the way you present your argument here.
No comment to this last part Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVZgxSAAoJEE4FgL32d2UkUz0H/3QylDmgYZWhNCG4Xawe2qxt 77oNsa/ZowsSJ8oXUpvr3LahhYvRwLYb87Dyoz+ASl6PKKJ/VW5jzfEEXlsRR5oU R/k5mJ1Yc2vRaBQOiGf7h6cUwxLciZO7ASxGC3mBN9m6ghwI0x7VHtYwaU0x7KEu PfWMxe7Byjb+NVN9gynxwzJWZ4RL2Yo2jxySi7aZqxgUdLDbuYCWMTWtjteC6wvP TrCyo2o6zM1eVjbnvsMtAvjjY+u2a2VXPZVSCKzESphACcUr4Epq8/eCMDIsIfK8 yt6QQQTmYIVCd+FB9ZY44u6Odu61dvhxJuso5VoFY14oVxRCsRmZmdtKRXri3bQ= =Fx38 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org