dstcleaner rev 0.1.1 is out!

Message

active · Post by **active** » Tue Apr 20, 2004 8:22 pm

Hi folks,
finally the revision 0.1.1 of dstcleaner is out!

Now it supports both Gentoo stable and unstable

Dstcleaner has the scope clean two critical Portage directories, which are:
DISTDIR: the source file repository
PORTAGE_TMPDIR: directories for temporary ebuild contruction

I think this could be a stable version. Now you don't need any more to uptade your dialog version to the "~x86" one; so if you use Gentoo from the stable branch you can mantain the current version of dialog.

- Usage:
Download the targzipped file from http://unixware.sf.net/dstcleaner-0.1.1.tar.gz
MD5sum: 142e1e33e55236daea1eed06f373f492
Extract the file to a temporary dir and copy the executable in your path (ex: /usr/local/sbin)
Just launch the program, it doesn't need extra arguments

- Bugs:
If you find bugs/problems (not rtfm ones

) please, let me know. I suggest however first to read the README.

Feedbacks are welcome. I hope you find this program useful, so I can request its insertion in the Portage tree.

Regards,

active · Post by **active** » Sun Apr 25, 2004 8:56 pm

Finally, there is a home page for dstcleaner.

You can reach it at:
http://unixware.sourceforge.net/dstcleaner/

Here you can download the current version of dstcleaner and check for newer versions.
For dstcleaner-0.1.1 the md5 is changed because of some little modifies to the README, so don't worry if you see two different md5sums (in the above post and in the site).

Thanks to all who have download it

bye

cylgalad · Post by **cylgalad** » Mon Apr 26, 2004 9:28 am

That's looking pretty interesting.
Now you should submit it with an ebuild to bugs.gentoo.org

TheButcher · Post by **TheButcher** » Fri May 07, 2004 6:53 pm

the program looks _VERY_ nice.
but i miss a function: since i'm sharing the portage-tree on my server, it would be nice to delete only outdated packages (prechecked) and not only not installed packages.

maybe you could implement that one?

active · Post by **active** » Tue May 11, 2004 6:09 pm

Thank you for your suggestion. In fact, I was thinking of a feature like this.
I will include that in the next release 0.2.0

Unfortunately, now my study takes all my time away.
So I cannot release anything for now

TheButcher · Post by **TheButcher** » Thu May 20, 2004 4:01 pm

oh damn...

i'd love to have that one!

ChopChopMasterOnion · Post by **ChopChopMasterOnion** » Thu May 27, 2004 3:47 am

i also have my distfiles on my server. I started the bare bones of such a project a while back in python but ended up not getting around to it. my main design requirements on mine were: (presented here as a suggestion for options)

allows choosing of any number of arch options, and keeping anything between the lowest selected arch current and the highest selected arch current, while allowing for a config file to mask particular packages from deletions (i.e. user-installed ebuilds, package masks such as requiring a specific version of galeon, which i had been doing at the time before I switched to firefox)

All was intended to run command line via SSH on my file server. Maybe I'll dust it off at some point, but if i did now i'd probably just learn perl and work on yours...i probably ought to learn perl anyway.

teedog · Post by **teedog** » Thu May 27, 2004 8:04 am

Could an ebuild be made for this?

active · Post by **active** » Sat May 29, 2004 3:17 pm

ChopChopMasterOnion wrote: allows choosing of any number of arch options, and keeping anything between the lowest selected arch current and the highest selected arch current, while allowing for a config file to mask particular packages from deletions (i.e. user-installed ebuilds, package masks such as requiring a specific version of galeon, which i had been doing at the time before I switched to firefox)

Hi, thank for your suggestions. In fact my idea was to make a "package.mask" file (inspired by the feature of portage) in which you can insert a list of package to keep; so by calling the script with an option (-a) all files/workdirs but those in that file will be cleaned.
Another useful feature is that of remove only very obsolete files (not included in portage anymore), so that a user can easily manage a central file server, sharing distfiles.

bye

active · Post by **active** » Sat May 29, 2004 3:33 pm

teedog wrote:Could an ebuild be made for this?

I proposed it on bugs.gentoo.org, but it's not yet been accepted. Anyway you can find it here:
http://bugs.gentoo.org/show_bug.cgi?id=49031

Instructions:
Create a dir under /usr/portage/app-portage/ called 'dstcleaner' and copy that text in a file called destcleaner-0.1.1.ebuild. After that, download the targzipped file from the site to the distfile dir and give a:

Code: Select all

ebuild destcleaner-0.1.1.ebuild digest

Now you should have all the necessary to make an:

Code: Select all

emerge dstcleaner

Obviously this file is not updated through the sync process.

regards,

active · Post by **active** » Sun Jun 20, 2004 9:01 pm

Hello,
a new version of dstcleaner is out! I named it 0.1.99 because it's a test version, but I hope it will become soon 0.2.0.

Anyone interested in testing would be appreciated. You can download the new dstcleaner here:
http://unixware.sourceforge.net/dstclea ... 1.99.pl.gz
this is a "packged" version, i.e. without comments, new lines, spaces, etc to reduce code size.

If you want to download the complete code, please visit here:
http://unixware.sourceforge.net/dstcleaner/sources.html

Features:
The main feature is the introduction of three usage modes:

Interactive mode: this is the same of the previous versions, a gui based on dialog.

Server mode: you may need this feature if you have a server (file repository) sharing the DISTDIR directory (distfiles). Dstcleaner checks (and removes) only for distfiles not included in the portage tree anymore. Any other distfile will be kept.

Auto mode: this mode is useful only if you want to keep a pool of distfiles, for example big files (OpenOffice.org). You have to specify a list of distfiles to keep in /etc/portage/dstcleaner.mask and dstcleaner will remove all stuff but those ones.

See the README.0.1.99 for more info: http://unixware.sourceforge.net/dstclea ... DME.0.1.99 and/or give:

Code: Select all

dstcleaner --help

Note: this version is a TEST version. It has no ebuild and no package. Please, use it only if you want to help me testing the code. For stable code and ebuild, wait the version 0.2.0.

Thank you all,

TheButcher · Post by **TheButcher** » Sun Jan 23, 2005 5:06 pm

Hi guys / active,

I've been using dstcleaner for ages now, but i encountered errors since app. one month. Maybe that's due to a portage update?
Your script keeps complaining about uninitialized variables, etc. (or maybe due to a perl-update?)

Anyways, when can we expect the 0.2.0?

I really love your piece of work

thx,
butch

active · Post by **active** » Sat Feb 12, 2005 10:26 pm

Hi TheButcher, thank you

.
Unfortunately I've disctontinued the updates to the dstcleaner because I'm rewriting it in C to make a more general (maybe modular) portage tool, but the time I can spend to this is always very little.

Anyway, related to your problem, I think it could be caused either from a new version of Perl or from the new version of portage (found in ~arch branches). On the stable Gentoo it's still working for me. Anyway for now I can't try it on a ~x86 system, but I'll do as soon as possible.

bye,
active

TheButcher · Post by **TheButcher** » Sun Feb 13, 2005 11:33 am

active wrote:Hi TheButcher, thank you .
Unfortunately I've disctontinued the updates to the dstcleaner because I'm rewriting it in C to make a more general (maybe modular) portage tool, but the time I can spend to this is always very little.

Anyway, related to your problem, I think it could be caused either from a new version of Perl or from the new version of portage (found in ~arch branches). On the stable Gentoo it's still working for me. Anyway for now I can't try it on a ~x86 system, but I'll do as soon as possible.

Well... Actually I'm also running a stable system. (not ~x86)

New tools? Sounds kewl. Is there a feature-list available yet? Or perhaps a release date?

thanks for your reply,
butcher