<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>Diego, el gnomo &#187; tips</title>
	<atom:link href="http://blogs.gnome.org/diegoe/category/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/diegoe</link>
	<description>Pisco Sour is GNOME's official cocktail</description>
	<lastBuildDate>Tue, 09 Aug 2011 10:59:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/2.5/pe/</creativeCommons:license>		<item>
		<title>How to use jhbuild, the easy way</title>
		<link>http://blogs.gnome.org/diegoe/2010/09/22/how-to-use-jhbuild-the-easy-way/</link>
		<comments>http://blogs.gnome.org/diegoe/2010/09/22/how-to-use-jhbuild-the-easy-way/#comments</comments>
		<pubDate>Thu, 23 Sep 2010 01:46:21 +0000</pubDate>
		<dc:creator>diegoe</dc:creator>
				<category><![CDATA[GNOME]]></category>
		<category><![CDATA[planetgnome]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://blogs.gnome.org/diegoe/?p=288</guid>
		<description><![CDATA[Inspired by André&#8217;s recent post I recalled that many people have gave me bad feedback about jhbuild. So I thought I might share some ideas and tips, here we go: Don&#8217;t use the jhbuild shipped by your distribution, use git master Only build what you need, buildone is your friend Prefer distro packages when possible, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://www.flickr.com/photos/diegoe/4006902583/" title="globos-o-clock by diegorm, on Flickr"><img src="http://farm3.static.flickr.com/2512/4006902583_7d1f559997_m.jpg" width="180" height="240" alt="globos-o-clock" /></a></p>
<p>Inspired by <a href="http://blogs.gnome.org/aklapper/2010/09/19/jhbuilding-gnome-3-0-no-fun/">André&#8217;s recent post</a> I recalled that many people have gave me bad feedback about jhbuild. So I thought I might share some ideas and tips, here we go:</p>
<ul>
<li>Don&#8217;t use the jhbuild shipped by your distribution, use git master</li>
<li>Only build what you need, buildone is your friend</li>
<li><em><span style="font-style: normal;">Prefer distro packages when possible, ALWAYS</span></em></li>
</ul>
<ul>
<li><strong>﻿I want to test the latest awesome version of RupertBrowser!<br />
</strong>jhbuild <em>buildone</em> rupert-browser</li>
</ul>
<ul>
<li><strong>But&#8230; I want to have RupertBrowser from master and it requires a LibBrowser that is not in my distro!<br />
</strong>jhbuild <em>buildone</em> libbrowser rupert-browser</li>
</ul>
<ul>
<li><strong>Awesome! But it seems RupertBrowser devs have a cool branch I&#8217;d like to automatically build, I bet you can&#8217;t do that!<br />
<span style="font-weight: normal;">Edit</span> </strong>your jhbuildrc:<br />
﻿branches['rupert-browser'] = (None, &#8216;new-cool-branch&#8217;)</li>
</ul>
<ul>
<li><strong>No wait, but that branch requires me to use the &#8211;enable-coolness switch for configure&#8230; how do I do that?<br />
<span style="font-weight: normal;">jhbuildrc again:</span><br />
</strong>module_autogenargs['rupert-browser'] = &#8216;&#8211;enable-coolness&#8217;</li>
</ul>
<ul>
<li><strong>This all looks nice, would you please show me a somewhat basic jhbuildrc file anyway?<br />
</strong>Sure, but don&#8217;t ask me to explain it all, use your bright mind or read jhbuild&#8217;s documentation, or config.py script (from jhbuild&#8217;s repo in git.gnome.org). Here it is:</li>
</ul>
<blockquote><p># if you are a committer to git.gnome.org, this is your line<br />
# ignore it if you are not a committer<br />
repos['git.gnome.org'] = &#8216;ssh://someone@git.gnome.org/git/&#8217;</p>
<p># see jhbuild&#8217;s repository for the classic modules or use a path to a custom one<br />
moduleset = &#8216;gnome-2-32&#8242;</p>
<p># don&#8217;t hit the internet for modules, just use what came with jhbuild<br />
use_local_modulesets = True</p>
<p># only build modules when there are new commits since the last time<br />
build_policy = &#8216;updated&#8217;</p>
<p># simultaneous build anyone?<br />
makeargs = &#8216;-j4&#8242;</p>
<p>### Branches<br />
branches['gtk+'] = (None, &#8216;awesome-new-stuff&#8217;)</p>
<p>### Checkout and install prefix<br />
checkoutroot = &#8216;/home/user/gnome/&#8217;<br />
prefix = &#8216;/home/user/gnome/build&#8217;</p>
<p>### Custom configuration<br />
autogenargs = &#8216;&#8211;disable-static &#8211;disable-gtk-doc &#8216;<br />
module_autogenargs['epiphany'] = autogenargs + &#8216;&#8211;something-magic&#8217;</p>
<p>### Extra env, you can set anything for the shell env here<br />
os.environ['CFLAGS'] = &#8216;-g -O2&#8242;</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gnome.org/diegoe/2010/09/22/how-to-use-jhbuild-the-easy-way/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Posting to pastebin from git</title>
		<link>http://blogs.gnome.org/diegoe/2010/02/11/posting-to-pastebin-from-git/</link>
		<comments>http://blogs.gnome.org/diegoe/2010/02/11/posting-to-pastebin-from-git/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 18:46:40 +0000</pubDate>
		<dc:creator>diegoe</dc:creator>
				<category><![CDATA[GNOME]]></category>
		<category><![CDATA[planetgnome]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[pastebin]]></category>
		<category><![CDATA[patches]]></category>
		<category><![CDATA[tip]]></category>
		<category><![CDATA[trick]]></category>

		<guid isPermaLink="false">http://blogs.gnome.org/diegoe/?p=178</guid>
		<description><![CDATA[I usually need to show someone a simple patch from a local git repo, my method was to run git format-patch and upload the result to my gnome.org userdir with a script conveniently called internets. This of course filled my userdir with garbage in the long run and also was a multiple step process. So [...]]]></description>
			<content:encoded><![CDATA[<p>I usually need to show someone a simple patch from a local git repo, my method was to run git format-patch and upload the result to my gnome.org userdir with a script conveniently called internets. This of course filled my userdir with garbage in the long run and also was a multiple step process.</p>
<p>So today, after a quick apt-cache search, I installed pastebinit, but then my problem was that there is no glue between this tool and git. Some googling took me to mentions of git-porcelains but I didn&#8217;t want to install that so I tried something simpler, a git alias.</p>
<p>I crafted this line for .gitconfig:<br />
<code>pastebinit = !sh -c 'git format-patch -1 –stdout $1 | pastebinit -f diff' -</code></p>
<p><b>Update:</b> Ray and Pablo shared some ideas in the comments, the alias is updated, thanks!.</p>
<p>That I can use like this:<br />
<code>git pastebinit [commit]</code></p>
<p>It runs and outputs the url of my new pastebin&#8217;d code <img src='http://blogs.gnome.org/diegoe/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> . I&#8217;m happy with it, but open to suggestions. Hope it&#8217;s useful for someone.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gnome.org/diegoe/2010/02/11/posting-to-pastebin-from-git/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Saving your neck when git-svn dcommit fails</title>
		<link>http://blogs.gnome.org/diegoe/2009/03/18/saving-your-neck-when-git-svn-dcommit-fails/</link>
		<comments>http://blogs.gnome.org/diegoe/2009/03/18/saving-your-neck-when-git-svn-dcommit-fails/#comments</comments>
		<pubDate>Wed, 18 Mar 2009 02:08:49 +0000</pubDate>
		<dc:creator>diegoe</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[dcommit]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[git-svn]]></category>
		<category><![CDATA[problem]]></category>

		<guid isPermaLink="false">http://blogs.gnome.org/diegoe/?p=105</guid>
		<description><![CDATA[Over the weekend I had to send some changes to an SVN repo. Thing is that I use git-svn to have all those XXI century benefits like local commits. Sadly I had some problems with git-svn, concretely it failed half the way through sending my really big number of changes. The result was that I [...]]]></description>
			<content:encoded><![CDATA[<p>Over the weekend I had to send some changes to an SVN repo. Thing is that I use git-svn to have all those XXI century benefits like local commits.</p>
<p>Sadly I had some problems with git-svn, concretely it failed half the way through sending my really big number of changes. The result was that I was left with uncommitted changes and missing commits after such set of changes. No need to say that I was really nervous about the state of my hard work of the week&#8230;</p>
<p>So after some desperate google searches and some questions to my personal GIT expert, <a href="http://blogs.gnome.org/desrt/">desrt</a>, I found this <a href="http://groups.google.com/group/google-code-hosting/browse_thread/thread/e0a6597f7f4c7739?pli=1">mail in google groups</a>. I reproduce the process here:</p>
<p><strong>How to save your neck when git-svn dcommit fails half through the process</strong></p>
<ol>
<li>Open <code>.git/logs/HEAD</code></li>
<li>Look for your most recent commit (note that these commits are sorted by &#8220;unix time&#8221;, although you can also find the latest one by reading the shortlog there</li>
<li>Confirm that the commit you found is the right one: git show <hash from log></li>
<li><code>git reset --hard <em>hash from log</em></code></li>
<li><code>git svn rebase</code></li>
<li><code>git svn dcommit</code></li>
</ol>
<p>This picks up where <strong>it left off</strong>, so you won&#8217;t loose anything, happy happy happy git <img src='http://blogs.gnome.org/diegoe/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> .</p>
<p>Hope this saved your neck like it saved mine. Other tips welcome <img src='http://blogs.gnome.org/diegoe/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> !</p>
<p><strong>Update:</strong> Mike lets me know that the commands were bad written because of html entities and stuff, fixed now.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gnome.org/diegoe/2009/03/18/saving-your-neck-when-git-svn-dcommit-fails/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How to know the return value of a command</title>
		<link>http://blogs.gnome.org/diegoe/2008/05/18/how-to-know-the-return-value-of-a-command/</link>
		<comments>http://blogs.gnome.org/diegoe/2008/05/18/how-to-know-the-return-value-of-a-command/#comments</comments>
		<pubDate>Sun, 18 May 2008 22:48:27 +0000</pubDate>
		<dc:creator>diegoe</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[commands]]></category>
		<category><![CDATA[return value]]></category>

		<guid isPermaLink="false">http://blogs.gnome.org/diegoe/2008/05/18/how-to-know-the-return-value-of-a-command/</guid>
		<description><![CDATA[Just do: $ echo $? and that&#8217;s it.]]></description>
			<content:encoded><![CDATA[<p>Just do:</p>
<p>$ echo $?</p>
<p>and that&#8217;s it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gnome.org/diegoe/2008/05/18/how-to-know-the-return-value-of-a-command/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Slow X rendering with sis driver</title>
		<link>http://blogs.gnome.org/diegoe/2008/04/14/slow-x-rendering-with-sis-driver/</link>
		<comments>http://blogs.gnome.org/diegoe/2008/04/14/slow-x-rendering-with-sis-driver/#comments</comments>
		<pubDate>Mon, 14 Apr 2008 21:44:43 +0000</pubDate>
		<dc:creator>diegoe</dc:creator>
				<category><![CDATA[bugs]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[googleme]]></category>
		<category><![CDATA[sis]]></category>
		<category><![CDATA[sisfb]]></category>
		<category><![CDATA[slow]]></category>
		<category><![CDATA[tip]]></category>
		<category><![CDATA[xorg]]></category>

		<guid isPermaLink="false">http://blogs.gnome.org/diegoe/2008/04/14/slow-x-rendering-with-sis-driver/</guid>
		<description><![CDATA[Everything slow when using X with the sis driver? Well, here it&#8217;s awfully slow, made me want to trash my old pc&#8230; but then I discovered this bug in Launchpad : lp #26637. Turns out that vesafb and vga16fb modules are responsible for this chaos. They seem to be stealing the memory managemen and hence [...]]]></description>
			<content:encoded><![CDATA[<p>Everything <strong>slow</strong> when using X with the sis driver? Well, here it&#8217;s awfully slow, made me want to trash my old pc&#8230; but then I discovered this bug in Launchpad : <a href='https://launchpad.net/bugs/26637' class='bug-link bug-link-lp'>lp #26637</a>.</p>
<p>Turns out that vesafb and vga16fb modules are responsible for this chaos. They seem to be stealing the memory managemen and hence making sis driver impossible to use due to it&#8217;s lack of descent performance.</p>
<p><em>What&#8217;s the fix?</em> <strong>Blacklist vesafb and vga16fb</strong> and add <em>sisfb</em> to <em>/etc/modules</em>. You can try to add video=sisfb in the boot line of the kernel (grub&#8217;s menu.lst) too.</p>
<p>Note that Fedora doesn&#8217;t have sisfb built and is forcing vesafb into the kernel for it&#8217;s graphical boot. Ubuntu is doing the same, but they also build sisfb as a module.</p>
<p>So if you are using Fedora, you are screwed unless you rebuild your kernel, if you are using Ubuntu or Debian, make sure vesafb is not loaded (nor vga16fb) and have sisfb loaded sometime before X starts.</p>
<p><em>How can you be sure it worked?</em> Grep /var/log/Xorg.0.log for &#8216;memcpy&#8217; and see if the MB/s rate is descent, you can try with and then without the sisfb module to check if it&#8217;s making a difference. Here it does.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gnome.org/diegoe/2008/04/14/slow-x-rendering-with-sis-driver/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/diegoe/category/tips/feed/ ) in 1.23649 seconds, on Feb 10th, 2012 at 11:45 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 12:45 am UTC -->
