<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel">
    <title>gmane.linux.gentoo.devel</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85773"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85772"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85771"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85770"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85769"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85768"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85767"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85766"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85765"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85764"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85763"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85762"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85761"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85760"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85759"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85758"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85757"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85756"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85755"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.gentoo.devel/85754"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85773">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85773</link>
    <description>&lt;pre&gt;




Usually the result is much better if you start from the Texinfo source
and use texi2any --html (included with sys-apps/texinfo itself) for
conversion.

Ulrich


&lt;/pre&gt;</description>
    <dc:creator>Ulrich Mueller</dc:creator>
    <dc:date>2013-05-24T06:48:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85772">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85772</link>
    <description>&lt;pre&gt;
This reminded me of my experience with info-files. Don't know how long ago
it was that I used them as I find google to be a much more useful
resource.

But you might be interested in the following:

* app-text/info2html
     Available versions:  (2.0) *2.0
        {{vhosts}}
     Homepage:            http://info2html.sourceforge.net/
     Description:         Converts GNU .info files to HTML

I haven't tried it myself yet. (Ignore the "hardmask" part in the output,
that's because the portage-filesystem is not automatically mounted)

--
Joost



&lt;/pre&gt;</description>
    <dc:creator>J. Roeleveld</dc:creator>
    <dc:date>2013-05-24T06:32:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85771">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85771</link>
    <description>&lt;pre&gt;(Late reply due to busy week, just want to clarify a small detail)

On Sun, May 19, 2013 16:34, Peter Stuge wrote:

Peter,

I agree, it is not likely, but this was in relation to embedded devices
where diskspace is often at a premium.
I will probably start a new thread on gentoo-user about inodes and
filesystems configuration later this year.

--
Joost

ps. no need to reply to this :)



&lt;/pre&gt;</description>
    <dc:creator>J. Roeleveld</dc:creator>
    <dc:date>2013-05-24T06:26:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85770">
    <title>Re: Re: robo-stable bugs</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85770</link>
    <description>&lt;pre&gt;On Thu, 23 May 2013 23:40:42 -0600
Ryan Hill &amp;lt;dirtyepic&amp;lt; at &amp;gt;gentoo.org&amp;gt; wrote:


The people that decided to change their way of using this keyword, did
so because setting it as early as possible helps maintainers that
forget to set it; I'm just following along this new approach.


Yet, they brought this keyword to live for a reason; a reason unclear
to me. Why is it unclear? Because nowadays people don't use it
consistently; some apply it early, some apply it when they CC.


Setting the keyword early helps here too, if everyone does so.

Otherwise you can do ...

1) a search in Keywording and Stabilization and exclude all bugs where
an arch is CC-ed, possible in the advanced search; or ...

2) obsessive summary grepping, for bugs with a wrong component set.

&lt;/pre&gt;</description>
    <dc:creator>Tom Wijsman</dc:creator>
    <dc:date>2013-05-24T05:58:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85769">
    <title>Re: robo-stable bugs</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85769</link>
    <description>&lt;pre&gt;On Wed, 22 May 2013 10:58:26 +0200
Tom Wijsman &amp;lt;TomWij&amp;lt; at &amp;gt;gentoo.org&amp;gt; wrote:



Okay, so what are you using the STABLEREQ keyword for that you want to set it
when the bug is filed but before archs are added?  If you want to see only
stabilization bugs you can search in the Keywording and Stabilization
component.  Can you suggest another way to search for stabilization bugs that
don't yet have archs CC'd (which is something I find rather useful)?


&lt;/pre&gt;</description>
    <dc:creator>Ryan Hill</dc:creator>
    <dc:date>2013-05-24T05:40:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85768">
    <title>Re: Re: robo-stable bugs</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85768</link>
    <description>&lt;pre&gt;On Thu, 23 May 2013 23:20:00 -0600
Ryan Hill &amp;lt;dirtyepic&amp;lt; at &amp;gt;gentoo.org&amp;gt; wrote:


No. Things can be broken. There are almost always bugs to fix.

New versions come with "bug" fixes too, users need these fixes.


Bug fixes are improvements too, so this definition is ambiguous.


Version bumps do not necessarily add features; just because they have
the potential to add features doesn't mean they don't fix actual bugs.


Using "enhancement" prevents them from importing upstream bug fixes.

&lt;/pre&gt;</description>
    <dc:creator>Tom Wijsman</dc:creator>
    <dc:date>2013-05-24T05:26:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85767">
    <title>Re: robo-stable bugs</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85767</link>
    <description>&lt;pre&gt;On Wed, 22 May 2013 13:00:46 +0200
Tom Wijsman &amp;lt;TomWij&amp;lt; at &amp;gt;gentoo.org&amp;gt; wrote:


Yes.  Nothing is broken.  There is no "bug" to fix.


It's not an "enhanced" bug, the bug is a request for an improvement (aka
enhance_ment_). Severity is meant to give you a way of categorizing open bugs by
how important they are, as you may want to fix actual bugs before worrying
about adding features.  Maybe you don't use bugzilla like that but some
people do and lumping these bugs in with the "normal" ones prevents them from
doing so.


&lt;/pre&gt;</description>
    <dc:creator>Ryan Hill</dc:creator>
    <dc:date>2013-05-24T05:20:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85766">
    <title>Re: [PATCH] gnome2.eclass does not respect ECONF_SOURCE</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85766</link>
    <description>&lt;pre&gt;

I guess I forgot to commit that to the tree when I posted it a few days
ago/week, w/e. Yeah commit that. My original commit was wrong.

&lt;/pre&gt;</description>
    <dc:creator>Doug Goldstein</dc:creator>
    <dc:date>2013-05-24T03:35:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85765">
    <title>Re: [PATCH multibuild.eclass] Use portable locking code from Fabian Groffen.</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85765</link>
    <description>&lt;pre&gt;
It can be tricky find out whether or not the underlying filesystem will 
behave well with flock. For example, maybe it will just fail temporarily 
due to lock exhaustion (ENOLCK), or maybe the filesystem doesn't support 
locking at all (ENOSYS).

Given all of the variables, it may be safest to use hardlink locks in 
any case, since they work reliably on practically any relevant 
filesystem. So if we do end up putting something in portability.eclass, 
maybe hardlink locks are the way to go. Alternatively, we could add some 
locking functions in the next EAPI, and let the package manager handle 
the implementation details.
&lt;/pre&gt;</description>
    <dc:creator>Zac Medico</dc:creator>
    <dc:date>2013-05-24T01:22:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85764">
    <title>Re: [gentoo-dev-announce] Bugzilla maintenance</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85764</link>
    <description>&lt;pre&gt;
far from what I expected :(&lt;/pre&gt;</description>
    <dc:creator>Theo Chatzimichos</dc:creator>
    <dc:date>2013-05-23T22:06:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85763">
    <title>Re: robo-stable bugs, the flipside</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85763</link>
    <description>&lt;pre&gt;
I believe the sources are hosted here

http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary

--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang


&lt;/pre&gt;</description>
    <dc:creator>Markos Chandras</dc:creator>
    <dc:date>2013-05-23T20:14:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85762">
    <title>Re: [PATCH] gnome2.eclass does not respect ECONF_SOURCE</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85762</link>
    <description>&lt;pre&gt;
Index: gnome2.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/gnome2.eclass,v
retrieving revision 1.120
diff -u -p -r1.120 gnome2.eclass
--- gnome2.eclass16 Jan 2013 23:01:02 -00001.120
+++ gnome2.eclass23 May 2013 19:31:00 -0000
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -122,7 +122,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; gnome2_src_configure() {
 # Remember to drop 'doc' USE flag from your package if it was only used to
 # rebuild docs.
 # Preserve old behavior for older EAPI.
-if grep -q "enable-gtk-doc" ${ECONF_SOURCE:-.}/configure ; then
+if grep -q "enable-gtk-doc" "${ECONF_SOURCE:-.}"/configure ; then
 if has ${EAPI:-0} 0 1 2 3 4 &amp;amp;&amp;amp; in_iuse doc ; then
 G2CONF="$(use_enable doc gtk-doc) ${G2CONF}"
 else
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -132,29 +132,29 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; gnome2_src_configure() {
 
 # Pass --disable-maintainer-mode when needed
 if grep -q "^[[:space:]]*AM_MAINTAINER_MODE(\[enable\])" \
-${ECONF_SOURCE:-.}/configure.*; then
+"${ECONF_SOURCE:-.}"/configure.*; then
 G2CONF="--disable-maintainer-mode ${G2CONF}"
 fi
 
 &lt;/pre&gt;</description>
    <dc:creator>Mike Frysinger</dc:creator>
    <dc:date>2013-05-23T19:31:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85761">
    <title>Re: robo-stable bugs, the flipside</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85761</link>
    <description>&lt;pre&gt;
By all means publish your script when done.  That seems like it would
be useful for many, and certainly there would be no objections when
used by package maintainers.  It is just automating a repetitive task.

Rich


&lt;/pre&gt;</description>
    <dc:creator>Rich Freeman</dc:creator>
    <dc:date>2013-05-23T19:29:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85760">
    <title>Re: [PATCH multibuild.eclass] Use portable locking code from Fabian Groffen.</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85760</link>
    <description>&lt;pre&gt;
this seems more appropriate for portability.eclass than other random places.  
there you can keep flock when it's available, or fall back to manual hacks like 
this.
-mike
&lt;/pre&gt;</description>
    <dc:creator>Mike Frysinger</dc:creator>
    <dc:date>2013-05-23T19:29:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85759">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85759</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/23/2013 04:02 AM, Daniel Campbell wrote:

It's not even that we don't agree with you, it's that you're asking
package and/or PM maintainers to do a bunch of work to save you a few
kilobytes of disk space. Their time is better spent elsewhere, I promise.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBAgAGBQJRnmuyAAoJEBxJck0inpOizroP/340iUw1ftiVKPh7I1cHFF19
9zBV7nW4hrQ25l0uViwLWtt9GMQ+TJK28cT3ru5/L5cQYIJpAmCpaB8bWGuLx1V3
O1XAtFJ16pu7gU72B7/0lGHIbxpl6qcMt+vKvuSnSQme6NANWadf0i3P3UvddGFS
zB4QSbyyePtnjEGEL1mbN3+nZM58u9c3m0vkYfbY7TahclhH0HX48nc+IJTxReVF
22Z/KC7UaGzsXfJR+BDC0RPH42WTaVGkdytE6yotR5JchnLUxujhShYbfumbJs4g
lRlP46bTlUzPEyriqRhdePsyEELDusACrIPzBK82BNEJP47WuO00kIi78CZ7dgyQ
ix82I2d1UQG7+UFEui+eBroDnAmTIPxOgxsIBYMNTc2pUJmnSqHva7iY8QMkBEvo
LddGMLFpjHj3D2LfM4L+RwZxpz0XRZCtZeDeYRnkXqEuPj7Df9/t+3LV5zljyho7
ppRJtBQvHGpB6G7z3HALyc8XIMXQmDtTBoE+CJms8Ifzd2Hs05Muo05he2C+dr8c
b0zDg/5LqG2XloszqB+1MxZNvL9O8vUpAZS9ZIu/Q8+4UpGXO5yPav42aHIWx+Zi
&lt;/pre&gt;</description>
    <dc:creator>Michael Orlitzky</dc:creator>
    <dc:date>2013-05-23T19:19:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85758">
    <title>Re: robo-stable bugs, the flipside</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85758</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 23/05/13 02:40 PM, Markos Chandras wrote:

homebrew, but it'd work.

Are the sources for the auto-stable etc. script posted somewhere?  I
don't think i've actually seen a URL at all in this thread (or the one
from a couple of months ago)..

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlGeZMgACgkQ2ugaI38ACPDeyQEAkgSoq/dJtCQjUBTJHSwTIk13
0odYcxYgcias45vE2vkA/j0UZRNFZbPtRhmyg9L5CO6LvfbAz92OY88wy0dcYYB5
=Nh5F
-----END PGP SIGNATURE-----


&lt;/pre&gt;</description>
    <dc:creator>Ian Stakenvicius</dc:creator>
    <dc:date>2013-05-23T18:49:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85757">
    <title>Re: robo-stable bugs, the flipside</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85757</link>
    <description>&lt;pre&gt;
I guess you could use pybugz + cron to do what you want.

--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang


&lt;/pre&gt;</description>
    <dc:creator>Markos Chandras</dc:creator>
    <dc:date>2013-05-23T18:40:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85756">
    <title>robo-stable bugs, the flipside</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85756</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Here's a new question on the robo-stable front -- I want to file a bug
(by hand, probably) on the next stable candidate for my package and
have the robo-stable script CC arches and STABLEREQ after 30 days
(assuming no other bugs pop up)

Is that doable?

(for those of us too lazy to put an entry in our calendars :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlGeW8wACgkQ2ugaI38ACPA9HgEAqofd3JKguCgiaDCS65kD23U1
rqc6POpLzA9oW/qmYqoA/0fmOLcgxxQnIQ79wzBWfF+RjNhcx3rt/wJBvFdiDkSm
=Ftge
-----END PGP SIGNATURE-----


&lt;/pre&gt;</description>
    <dc:creator>Ian Stakenvicius</dc:creator>
    <dc:date>2013-05-23T18:11:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85755">
    <title>Re: robo-stable bugs</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85755</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 22/05/13 07:03 PM, Rick "Zero_Chaos" Farina wrote:

I expect the script can probably work on the basis that any status
other than what the bug was filed with is an exclusion for the
auto-stable pass (confirmed-&amp;gt;unconfirmed in this case).

However, yes I agree it would be very useful to have a link to some
page, describing the the whole autostabilization process (what the
script does, how devs can interact with it).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlGeEiUACgkQ2ugaI38ACPAeNAD/QcSQL7yufe2YpKTb2cV2VP0r
WJoHs4uozZIsRDrYXjcA/1icODLSi/sjCl6+zRLjdiUKvRJbKiz2FZRzAtZ3IjFN
=B9Pd
-----END PGP SIGNATURE-----


&lt;/pre&gt;</description>
    <dc:creator>Ian Stakenvicius</dc:creator>
    <dc:date>2013-05-23T12:57:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85754">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85754</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 23 May 2013 03:02:30 -0500
Daniel Campbell &amp;lt;dlcampbell&amp;lt; at &amp;gt;gmx.com&amp;gt; wrote:


These things are likely documented on websites on the internet, on wikis
related to Gentoo and on our forums; if not, you can always start a new
thread on the Gentoo Forums, a new discussion on social media (Google+,
#gentoo-chat on FreeNode, the gentoo-user ML, ...) or so.

Feel free to ping me by mail if you do so, I'll be happy to help...

If you are an user that wishes to contribute to gentoo-dev, please stay
on topic in the thread you are discussing in as well as with the goal
of the ML; if you think we should implement or document space cleaning
better, then you're always welcome to start a new thread about that.

Thank you in advance.

- -- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij&amp;lt; at &amp;gt;gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D
-----BEGIN PGP SI&lt;/pre&gt;</description>
    <dc:creator>Tom Wijsman</dc:creator>
    <dc:date>2013-05-23T09:46:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.gentoo.devel/85753">
    <title>Re: Re: Making systemd more accessible to "normal" users</title>
    <link>http://permalink.gmane.org/gmane.linux.gentoo.devel/85753</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/23/2013 01:41 AM, Michał Górny wrote:

I can't speak for others who wish to rid their systems of systemd, but
personally I look for any excessive use of space on my HDD, despite it
being rather large. Since you brought it up, which packages can you
think of that most or all Gentoo boxes will have that take up more
considerable amounts of files or disk space? I'm honestly interested
in *anything* that lowers the disk usage of my OSes; to a point,
anyway. Supporting X or Y codec or feature in the kernel would be more
important than saving 50kB in the kernel binary, for instance.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRnc0WAAoJEJUrb08JgYgH8I0H/RqmDrgkexeLCaBB2RDXKyjv
EAZeVQvjNuxzTJz5Qr+CNHgpAk58YCZVcH+IBspD3Ks1DatKzyoSxuwwG70lfDmX
k/Rp9T+YL/gZnC3Ey6x/ScAwZIDlDbbZO3xwOt+3fHZEhiCE4IFEsCiaWCwEGHV1
NrROzDRBICYc9KePAtksqvYEovu8ex2JCAbthHhDb7fKvr3TqWCBzWtbSM&lt;/pre&gt;</description>
    <dc:creator>Daniel Campbell</dc:creator>
    <dc:date>2013-05-23T08:02:30</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.gentoo.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.gentoo.devel</link>
  </textinput>
</rdf:RDF>
