<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>53675</bug_id>
          
          <creation_ts>2004-06-11 15:00 0000</creation_ts>
          <short_desc>durep-0.8.1.ebuild (new package)</short_desc>
          <delta_ts>2005-02-12 07:13:14 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <keywords>EBUILD</keywords>
          <priority>P2</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>stsp@binarchy.net</reporter>
          <assigned_to>base-system@gentoo.org</assigned_to>
          <cc>stsp@binarchy.net</cc>

      

      
          <long_desc isprivate="0">
            <who>stsp@binarchy.net</who>
            <bug_when>2004-06-11 15:00:47 0000</bug_when>
            <thetext>This is a nice utility. This guy using debian showed it to me. I did an emerge
search and couldn&apos;t find it so here is an ebuild for it.

This is an excerpt from the durep website (http://www.hibernaculum.net/durep): 

Disk Usage Reporter is a perl script designed for monitoring disk usage in a more visual way than du. The du program works fine but doesn&apos;t allow a lot of control over how the results are displayed. This perl script is designed to produce output more useful for reports.

Although durep can produce text output similar to du, its real advantage is that it allows you to navigate through the directory structure as web pages. Each page shows bar graphs for entries so it is easy to see immediately which directory is using the most storage space. The report generated can be configured in several ways (hiding directories, collapsing directory entries, hiding entries below certain sizes, etc).</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>stsp@binarchy.net</who>
            <bug_when>2004-06-11 15:01:41 0000</bug_when>
            <thetext>Created an attachment (id=33105)
durep-0.8.1.ebuild
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-02-11 19:34:25 0000</bug_when>
            <thetext>add 0.9 to portage, thanks :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>stsp@binarchy.net</who>
            <bug_when>2005-02-12 05:59:25 0000</bug_when>
            <thetext>wow, this took only 8 months...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>g2boojum@gentoo.org</who>
            <bug_when>2005-02-12 06:54:13 0000</bug_when>
            <thetext>By adding this package to portage, SpanKY has agreed to maintain this package for the forseeable future.  Thus, adding a new package is not a trivial event, since right now the average load is about 30 packages to maintain per developer.  (SpanKY actually maintains far more than that.)  The most effective way to speed up the time to get a favorite package into portage is to become a developer and maintain it yourself.  The next most effective way is to have a lot of people comment on the new-package bug that the package is the best thing since sliced bread, since if the new package is only going to be used by one person then it&apos;s probably not worth maintaining.  Thus, 8 months doesn&apos;t seem all that unfair.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>stsp@binarchy.net</who>
            <bug_when>2005-02-12 07:13:14 0000</bug_when>
            <thetext>&quot;adding a new package is not a trivial event&quot;

I know, and I was not _that_ serious.
I should probably let the irony shine through a bit more next time :)

&quot;The most effective way to speed up the time to get a favorite package into portage is to become a developer and maintain it yourself.&quot;

Great, where do I sign up?
There are a few little unimportant ebuilds I&apos;d like to maintain.
For example, I would take durep, and mved, if possible (I&apos;m mved upstream).

&quot;The next most effective way is to have a lot of people comment on the new-package bug that the package is the best thing since sliced bread&quot;

To be honest, I haven&apos;t been using durep for quite a while now.
I remember that it (version 0.8.1) was rather slow for large directory trees,
so I started using du again. So durep is definitely not the best thing since
sliced bread. I&apos;d thus go for the most effective way to speed up the time to
get a favorite package into portage, if possible :)</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>33105</attachid>
            <date>2004-06-11 15:01 0000</date>
            <desc>durep-0.8.1.ebuild</desc>
            <filename>durep-0.8.1.ebuild</filename>
            <type>text/plain</type>
            <data encoding="base64">IyBDb3B5cmlnaHQgMTk5OS0yMDA0IEdlbnRvbyBUZWNobm9sb2dpZXMsIEluYy4KIyBEaXN0cmli
dXRlZCB1bmRlciB0aGUgdGVybXMgb2YgdGhlIEdOVSBHZW5lcmFsIFB1YmxpYyBMaWNlbnNlIHYy
CiMgJEhlYWRlcjogJAoKREVTQ1JJUFRJT049IkEgcGVybCBzY3JpcHQgZGVzaWduZWQgZm9yIG1v
bml0b3JpbmcgZGlzayB1c2FnZSBpbiBhIG1vcmUgdmlzdWFsIHdheSB0aGFuIGR1LiIKSE9NRVBB
R0U9Imh0dHA6Ly93d3cuaGliZXJuYWN1bHVtLm5ldC9kdXJlcC8iClNSQ19VUkk9Imh0dHA6Ly93
d3cuaGliZXJuYWN1bHVtLm5ldC9kb3dubG9hZC8ke1B9LnRhci5neiIKTElDRU5TRT0iQXJ0aXN0
aWMiClNMT1Q9IjAiCktFWVdPUkRTPSJ+eDg2IiAKUkRFUEVORD0iZGV2LWxhbmcvcGVybCIKCnNy
Y19pbnN0YWxsKCkgewoJZG9iaW4gZHVyZXAKCW1ha2UgZG9jICYmIGRvbWFuIGR1cmVwLjEKCWRv
ZG9jIEJVR1MgQ0hBTkdFUyBSRUFETUUgVEhBTktTIFRPRE8KfQo=
</data>        

          </attachment>
    </bug>

</bugzilla>