15 Nov
2017
15 Nov
'17
15:51
On Wed, Nov 15, 2017 at 10:45 AM, Henne Vogelsang <hvogel@opensuse.org> wrote:
> Hey,
>
> On 15.11.2017 16:33, Todd Rme wrote:
>> On Wed, Nov 15, 2017 at 8:30 AM, Henne Vogelsang <hvogel@opensuse.org> wrote:
>>> On 14.11.2017 19:29, Todd Rme wrote:
>>>
>>>> Thinking about what we need for python3 conversion long-term, a few
>>>> issues have come to mind that currently aren't addressed well in the
>>>> macros or previous discussions:
>>>>
>>>> 1. -> 4.
>>> 5. packages that include files outside of sitelib/arch. This fails
>>> during verification because of the file conflicts.
>>
>> Those are usually python version-independent. That is the idea of
>> having a "python-foo-data" package convention for such files.
>
> And who decides which python*-foo package you use? :-)
>
> Henne
>From all the examples I have seen the "python*-foo" packages require
the "python-foo-data" package (the name varies). If the files are
version-independent it doesn't matter which one they are pulled from.
In cases I have seen where they are version-dependent, they can be
renamed to use "%{$python_bin_suffix}". That is typically the case
when .desktop files are involved, but those need to use
"%{$python_bin_suffix}" anyway.
The only case I am aware of where neither of these approaches work is
with jupyter notebook extensions, but since we only ship the python3
version of the notebook executable, we also only ship the python3
version of the notebook extensions.
Do you have a specific situation where none of these approaches work?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org