This is a nice utility. This guy using debian showed it to me. I did an emerge search and couldn'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'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).
Created attachment 33105 [details] durep-0.8.1.ebuild
add 0.9 to portage, thanks :)
wow, this took only 8 months...
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's probably not worth maintaining. Thus, 8 months doesn't seem all that unfair.
"adding a new package is not a trivial event" I know, and I was not _that_ serious. I should probably let the irony shine through a bit more next time :) "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." Great, where do I sign up? There are a few little unimportant ebuilds I'd like to maintain. For example, I would take durep, and mved, if possible (I'm mved upstream). "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" To be honest, I haven'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'd thus go for the most effective way to speed up the time to get a favorite package into portage, if possible :)
