On Thu, Nov 10, 2016 at 11:18 AM, Andreas Schwab <schwab@suse.de> wrote:
On Nov 10 2016, jan matejek <jmatejek@suse.cz> wrote:
On 10.11.2016 16:45, Andreas Schwab wrote:
On Nov 10 2016, jan matejek <jmatejek@suse.cz> wrote:
devel:languages:python itself builds for distros as old as SLE11. we might drop that soon, but still there's SLE12_backports, 13.2 and both Leaps, both of which are "old distros" for the purpose of this discussion, seeing as they're already released.
So do many personal / topical / private repositories.
We need to support all of that, otherwise nobody will switch to the new macros.
No problem, set up the project config of devel:languages:python as you like. That's your anchor.
But then everyone who wants to build a python package would need to fork from d:l:py. This is not the case in practice.
Any project that wants the updated python-rpm-macros package will either have to build against d:l:py (or factory) or carry over the corresponding project config settings. That includes any :Update project.
Andreas.
What percentage of projects have a python package in them? Since these are _new_ macros, what would be the danger of adding them to the base distros: 13.1, 13.2, 42.1, 42.2 and factory. If there is a concern some projects already define them for a different purpose, couldn't OBS be scanned for existing macros with the same name and then eliminate the conflicts prior to instituting these new macros. I for one, would prefer to see these macros either global to OBS, or at least global to the openSUSE repositories. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org