Hi Joe,
I would also like to see some good tool for auto-updates especially connected with
auto-rebuilds. I already made a commitment to myself that I will try to implement
something a while ago. I will most likely try to go with polisher[1] and build on top of
it since a lot of stuff like infrastructure tools integration are already implemented
there. But this is definitely a long run. Most of our updates and rebuilds in Fedora
requires really a lot of manual work. I probably don't see any issues with gem2rpm
handling some sort of updates although you are probably aiming on simple things that can
be achieved by a short bash/ruby script. But that being said I will definitely try out
anything you come up with.
Regards
Josef
[1]
https://github.com/ManageIQ/polisher
----- Original Message -----
From: "Joe Rafaniello" <jrafanie(a)redhat.com>
To: ruby-sig(a)lists.fedoraproject.org
Sent: Monday, June 23, 2014 5:20:01 PM
Subject: gem2rpm and upgrades of existing rpms
Hi all,
Does anyone use gem2rpm to upgrade an existing rpm to new versions of upstream gems?
I'm contemplating working on a pull request to make gem2rpm aware of an existing .spec
file and only update specific sections such as: version, requires, buildrequires, and
adding a changelog. As it is now, it overwrites the existing rpm spec, removing any
changelog entries, etc.
Is this a good idea? What do others do to regenerate the updated version,
requires/buildrequires to avoid human error?
Thanks,
--
Joe Rafaniello
_______________________________________________
ruby-sig mailing list
ruby-sig(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig