OpenSUSE packages

[Guillaume Gardet]

Le 30/12/2014 16:41, Dirk Hohndel a écrit :
> On Tue, Dec 30, 2014 at 04:17:12PM +0100, Guillaume Gardet wrote:
>> Le 30/12/2014 16:05, Dirk Hohndel a écrit :
>>> On Tue, Dec 30, 2014 at 03:20:54PM +0100, Guillaume Gardet wrote:
>>>> Le 22/12/2014 21:09, Dirk Hohndel a écrit :
>>>>> On Mon, Dec 22, 2014 at 06:40:51AM -0800, Dirk Hohndel wrote:
>>>>>> On Mon, Dec 22, 2014 at 10:19:11AM +0100, Guillaume Gardet wrote:
>>>>>>> Le 20/12/2014 06:40, Dirk Hohndel a écrit :
>>>>>>>> We now have official OpenSUSE packages - available at
>>>>>>>> http://software.opensuse.org/download.html?project=home:Subsurface-Divelog&package=subsurface.
>>>>>>>> I updated the Downloads page accordingly.
>>>>>>> Could you enable build for openSUSE 13.1 too, please?
>>>>>> I'd love to, if I could figure out how to get it to pull the Qt5 packages
>>>>> >from the KDE:QT53 project. There's a bit of spec file magic that I clearly
>>>>>> haven't quite figured out, yet.
>>>>> OK, with the help of some nice people on the opensuse-buildservice IRC
>>>>> channel I think I have figured this out. openSUSE 13.1 is now available as
>>>>> well - I tested this in a freshly installed VM and all looks good...
>>>> So far, it runs fine on my 13.1. Thanks. :)
>>> Yes. The Tumbleweed builds have been broken for a few days and the error
>>> message makes no sense to me. It looks like the rpm is packaged and
>>> everything and then it fails with a non-sensical error.
>> I will try to have look at it. I think I already encountered this error once.
>>
>> You should rename your daily build package "subsurface-daily" or
>> "subsurface-unstable", otherwise, people will install latest subsurface
>> from your repo and then they got your daily instead of your stable
>> subsurface.
> I was wondering about this... that means I need a different spec file that
> renames the executable and the package... but then there is the
> ssrfmarblewidget.so that also would have to have two different names. This
> gets crazy pretty fast.
>
> I'm not sure what a good way around this mess would be.

I think the easiest way is just to rename the RPM package (spec filename and "Name: XXX" line) and leave exec name as is. You may add a "Conflicts: Subsurface" line in your spec so that people cannot install both.

Guillaume