Re^3: Cleaning out .cpan/build directory

Actually cpan knows how to do that.

It has a clean command and will clean the .build folder when it gets too big.

Using the temp area is not such a swell idea since you might want to inspect the files in the .build folder and the temp area has the habit of getting emptied at inopportune moments. At least on Windoze. :(

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Comment on Re^3: Cleaning out .cpan/build directory Select or Download Code

Replies are listed 'Best First'.
Re^4: Cleaning out .cpan/build directory by ikegami (Patriarch) on May 25, 2011 at 18:41 UTC
Executables often can't be run from people's temp directory, so it's not an option. You could prevent the build folder from getting cleaned automatically by setting a large value for `o conf build_cache`.	[reply] [d/l]
Re^4: Cleaning out .cpan/build directory by John M. Dlugosz (Monsignor) on May 25, 2011 at 20:06 UTC
The help says "clean" is "make clean" and is in the same set with get, make, test, install. That is, it runs make clean in a particular build directory, not delete those build directories themselves. Is that not right?	[reply]
Re^5: Cleaning out .cpan/build directory by CountZero (Bishop) on May 26, 2011 at 15:55 UTC
The `clean` command works on a per distribution basis only. I never checked if it also deletes the directory itself too. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply] [d/l]


Think about Loose Coupling
	PerlMonks