gem2rpm and upgrades of existing rpms

[Mo Morsi]

On 06/25/2014 10:15 AM, Joe Rafaniello wrote:
>> Well, what is in the upstream fermig repository and what I am actually
>> using during migration periods is not always the same. From my point of
>> view, it is one shot library, which should be ideally used once a year
>> (or how often the guidelines are updated) and that is it.
>>
>> Actually, I see where are you aiming, i.e. the upgrade of gem is good
>> opportunity to update the .spec, etc. but from tooling POV, it is easier
>> to do it in two steps, e.g. update everything in Fedora when guidelines
>> are updated and upgrade to new version when new version is released.
>>
>> Vít
>>
> Corrected the line 7) below...
>
> Thanks, this is great information.
> I think it's easier to add "update" functionality to gem2rpm by ensuring the template and spec both get updated to latest conventions.


Would have to agree w/ Vit on this one, it'd be easier to split things
into multiple separate use cases:

- generate a new spec from scratch

- updated a single package version to new specifications

- updating a single package between versions

The Unix philosophy is to build and use simple tools that do simple
things well. We should try and nail each of these down individually
before trying to abstract all three into a single stage / tool.


> It's really complicated to try to apply changes from a spec generated with new conventions into a spec using old or no conventions.

Have you attempted this? Perhaps some code would better illustrate what
you are going for?

  -Mo