[X2Go-Dev] Bug#755: cannot upgrade x2goServer on fedora 20 using yum

[Orion Poplawski]

On 03/23/2015 09:35 AM, Mike Gabriel wrote:
> Hi Mihai, hi Orion,
> 
> On  So 22 Mär 2015 03:12:31 CET, Mihai Moldovan wrote:
> 
>> On 18.03.2015 11:02 PM, Orion Poplawski wrote:
>>> On 03/18/2015 12:10 AM, Mihai Moldovan wrote:
>>>> On 25.01.2015 05:43 AM, Orion Poplawski wrote:
>>>>> [...]
>>>>>
>>>>> I could probably have the Fedora x2goserver package provide
>>>>> x2goserver-extensions to help with such situations.
>>>> Please do. For both Fedora and EPEL, if possible.
>>>>
>>>> I just had to work around this in
>>>> http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebindings.spec;h=2e2485fe4e43d866ac09cd902fc45ce327ae8285;hp=49b80bed94a0e0455fe74ed824ce13e50695206a;hb=HEAD;hpb=df8c930d9294de22fa0aa14267ee4942f70b8939
>>>>
>>>>
>>>> Thank you very much in advance.
>>>> [...]
>>> Sure, but why even have the x2goserver-extensions sub-package?  It requires
>>> x2goserver and x2goserver requires it, so you can't install one without the
>>> other.
>>
>> To be *perfectly honest*? I don't know, ask Mike#1.
> 
> it's again related to mapping the .deb packaging to the way we package for
> .rpm distros.
> 
> First, the objective was: having the same package names for both ways of
> packaging, so that people can read/write docs alike for both distro types.
> 
> Second, in .spec files, there is no such thing as a "Recommends:" package
> relationship, so I used "Requires:" for what is under "Recommends:" in the
> .deb way of packaging.
> 
> Third, the package x2goserver-extensions and x2goserver-xsession have been
> contributed by me to X2Go. In the beginning, I wanted to make sure to provide
> some extra stuff that people can add to their X2Go Server installations. I did
> not want to enforce their usage on already deployed systems.
> 
> Then... The more bugs had been reported against x2goserver-xsession, the more
> I elevated the level of dependency (from nothing to Suggests: to Recommends:).
> 
> About x2goserver-extensions: keeping it as a separate package allows people
> (with a .deb based distro--it is under Recommends: IIRC) to remove the package
> and disable extensions globally. But now that several of our own X2Go
> components use the extension add-on package, this has virtually become a
> not-to-do scenario, actually.
> 
> I hope that helps to clarify the history of those add-on packages, that should
> actually by merged into the main x2goserver package. And...
> 
>   o Don't forget to scan the wiki.x2go.org site for those package names and
> update the passages appropriately.
>   o Don't forget to provide transitional dummy package that allow smooth
> upgrade of systems having old versions of those packages installed.
> 
> light+love
> Mike

Thanks, Mike.   I'm pretty sure I've asked this before as well.  I'll try not
to ask it again.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at nwra.com
Boulder, CO 80301                   http://www.nwra.com