[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-packaging
Subject:    Re: [opensuse-packaging] Re: Packaging python singlespec applications
From:       Todd Rme <toddrme2178 () gmail ! com>
Date:       2017-09-20 18:43:00
Message-ID: CADb7s=uV3y9tR0yJW7nSbRA8si0ozY3T5osM1nnwO0pnEqnW4g () mail ! gmail ! com
[Download RAW message or body]

On Tue, Sep 19, 2017 at 1:08 AM, Simon Lees <sflees@suse.de> wrote:
>
>
> On 19/09/17 03:40, jan matejek wrote:
>> On 13.9.2017 17:18, Todd Rme wrote:
>>> On Wed, Sep 13, 2017 at 7:42 AM, jan matejek <jmatejek@suse.com> wrote:
>>>> hello,
>>>>
>>>> On 12.9.2017 21:28, Todd Rme wrote:
>>>>> First, it would be nice if %python_subpackages allowed us to specify
>>>>> additional packages to manage. These would be packages named using
>>>>> "%package -n foo" that we nevertheless want to have multiple versions
>>>>> of. The macros would then create a set of packages
>>>>> "foo-%{python_bin_suffix}". So for example we might say
>>>>> %{python_subpackages spyder}. If we did that, we would get
>>>>> "spyder-3.6" and "spyder-2.7", with Requires, Provides, Obsoletes, and
>>>>> %files all handled appropriately for the given python version.
>>>>
>>>> I kind of like this, but don't quite understand how you would use it.
>>>> You're presuming the package is called "spyder"? or "python-spyder"? what is the subpackage here?
>>>
>>> So you would still have "Name: python-spyder" that would be handled
>>> normally (although it might not have a %files section).  There would
>>> be a subpackage  "%package -n spyder". The "spyder" %package,
>>> %description, %files, etc. would be replaced by
>>> "spyder-%{python2_bin_suffix}" and "spyder-%{python3_bin_suffix}".
>>
>> Why is the master package called "python-spyder"?
>>
>> Wouldn't it be better, in this case, to change the logic for packages that aren't called "python-foo"?
>> Like, "python-foo" converts to "python2-foo" and "python3-foo"
>> whereas "spyder" converts to "spyder-2.7" and "spyder-3.7"
>> ?
>>
>> Is there a usecase where we want both of these behaviors?
>> If yes, maybe this should be done by a single option switch to %python_subpackages.
>
> I would have thought the better question is do we really need 2 versions
> of python applications 1 built with each, as a user of spyder or any
> other python app why would I care if its built with python2 or python3
> as long as it works.

The problem is that you cannot use spyder3 to do python2 development
and vice versus.  As long as the spyder upstream supports both python2
and python3 and we as a distro are providing both python2 and python3
in general, I think the spyder IDE should support both as well.
-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]