<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/11/2014 09:59 AM, Matěj Cepl
wrote:<br>
</div>
<blockquote cite="mid:slrnlpgo5q.474.mcepl@wycliff.ceplovi.cz"
type="cite">
<pre wrap="">That is not The Fedora Way™ … I have been always proud, that in
Fedora it is useless to have PPAs, because we have one shared
PPA on which everybody can work — the Fedora itself.
Couldn’t we just make single-spec package (with some %ifs if
necessary) building on supported Fedoras (F19, F20, Rawhide, at
the moment) and the last EPEL (for a moment, I would support
EPEL-6 as well, but after half-a-year or so I would stick with
just EPEL-7)?
Would anybody mind if I just build the latest sword and xiphos
for these repos?</pre>
</blockquote>
As Greg and I have chatted in IRC, the perspective he's offered is
that building for older releases is for bug and security
vulnerabilities. I disagree with this, but if that's Policy, I
don't have a lot of say. Obviously there are bug fixes in each
release, and I would think that justifies building for all
currently-supported releases. That's why I built Sword and Xiphos
packages last evening for F19, which I've now been told work fine on
F20, too.<br>
<br>
I of course won't mind if current versions get built for the
official repos.<br>
<blockquote cite="mid:slrnlpgo5q.474.mcepl@wycliff.ceplovi.cz"
type="cite">So, should I close it as CANTFIX (or WONTFIX)?
</blockquote>
I would say "already fixed, by abandoning an old toolkit" but you
can pick whatever notation is appropriate.
<blockquote cite="mid:slrnlpgo5q.474.mcepl@wycliff.ceplovi.cz"
type="cite">
<pre wrap="">So needinfo asking what’s the relevance of KDE? Does the GUI
uses something weird like “Gnome theme making Gnome apps looking
like KDE ones” (what’s its name)? It used to lead to many
crashes, but I don’t know if such animal still exists in
KDE4/Gnome3 world.
</pre>
</blockquote>
I'm unaware of any such animal at all. From my perspective, any
interaction with KDE is simply wrong. So yes, need to understand
how libproxy comes into the picture in the first place, and why it
wants to interact with KDE. Xiphos has no proxy support at all --
why is anything down there asking for <i>either</i> libproxy <i>or
</i>KDE?<br>
</body>
</html>