<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Luke Faraone &#187; autokey</title>
	<atom:link href="http://luke.faraone.cc/blog/tag/autokey/feed/" rel="self" type="application/rss+xml" />
	<link>http://luke.faraone.cc/blog</link>
	<description></description>
	<lastBuildDate>Fri, 25 Jun 2010 14:13:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Sometimes things get complicated&#8230; (Handling upgrades from Karmic)</title>
		<link>http://luke.faraone.cc/blog/2010/01/sometimes-things-get-complicated-handling-upgrades-from-karmic/</link>
		<comments>http://luke.faraone.cc/blog/2010/01/sometimes-things-get-complicated-handling-upgrades-from-karmic/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 03:36:58 +0000</pubDate>
		<dc:creator>luke</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[autokey]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[packaging]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[upgrades]]></category>

		<guid isPermaLink="false">http://luke.faraone.cc/blog/?p=116</guid>
		<description><![CDATA[I&#8217;m the package maintainer for Autokey in Debian. Upstream recently changed from using GTK+ to Qt4, which caused more than one complaint from users of testing. The GTK+ version of the package is published in Ubuntu 9.10 Karmic. While upstream is continuing to do regular releases of the GTK version, they are focusing on the [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m the <a href="http://packages.debian.org/unstable/kde/autokey">package maintainer</a> for <a href="http://autokey.googlecode.com">Autokey</a> in Debian. Upstream recently changed from using GTK+ to Qt4, which caused <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=545868">more</a> than <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=545868">one</a> complaint from users of <a href="http://www.debian.org/releases/testing/">testing</a>.</p>
<p>The<a href="http://autokey.googlecode.com/files/autokey-gtk_0.61.2.tar.gz"> GTK+ version</a> of the package is published in <a href="https://edge.launchpad.net/ubuntu/karmic">Ubuntu 9.10 Karmic</a>. While upstream is continuing to do regular releases of the GTK version, they are focusing on the <a href="http://autokey.googlecode.com/files/autokey_0.61.2.tar.gz">KDE version</a> and have changed <code>autokey</code> to refer to the KDE version, while renaming the GTK version (formally <code>autokey</code>) to <code>autokey-gtk</code>. To make matters worse, upstream releases both as separate tarballs, and the packages conflict with one another.  (due to technical limitations)</p>
<p>What&#8217;s the proper proceedure for handling this in Ubuntu? Should <code>-gtk </code><strong>conflict</strong> with <code>autokey</code>, <strong>replace</strong> it, with  <code>autokey-qt </code>being available as an option, or should I just keep things as they are and have the package &#8220;change out from under&#8221; users when they upgrade?<code></code></p>
]]></content:encoded>
			<wfw:commentRss>http://luke.faraone.cc/blog/2010/01/sometimes-things-get-complicated-handling-upgrades-from-karmic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
