[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Any chance of backporting gnome-keyring or kwallet to RHEL 4 compatibility? Just asking....

From: Stefan Sperling <stsp_at_elego.de>
Date: Sat, 31 Mar 2012 17:01:14 +0200

On Sat, Mar 31, 2012 at 10:50:31AM -0400, Nico Kadel-Garcia wrote:
> I'm spending way too much time backporting 1.6.17 work to RHEL 4, to
> publish for Repoforge. So far so good, I'm working from Mike Bauer work at
> plos.org, and tying it to my old Repoforge work for 1.6.x, and that's based
> on Fedora 16 source RPM's on the last go-round. No big problem so far, it's
> just a lot of testing changes one at a time.
> But there are some side packages that just won't work for RHEL 4. In
> particular, the "--with-kwallet" option isn't workable with such an old
> KDE, and the "--with-gnome-keyring" won't build with such an old DBus.
> (I've got workarounds for --with-kwallet for RHEL 6 compilation, but
> --with-kwallet doesn't work for RHEL 5, either.)
> I can disable them from package compilation for RHEL 4, but is there anyone
> familiar enough with those tools to try backporting them? I realize RHEL 4
> is on extended support only, but sometimes migrating people off of old
> systems really benefits from access to supported source control tools.

Who are you building these package for? Do the users really require the
kwallet/gnome password store features? If I were you and I was building
these RHEL4 packages for the general public I would decide that these
features are not critical enough to warrant the backporting effort.

Keep in mind that you are essentially talking about backporting large
chunks of KDE/Gnome and the underlying toolkits (QT and GTK). I doubt
anybody would want to do this for fun.
Received on 2012-04-01 02:01:53 CEST

This is an archived mail posted to the Subversion Users mailing list.