[Compilercache-general] Hmm, an idea came up my mind...

[Joachim B. <ma...@jo...>]

Hi all,

it's been a bit silent here. anyway, what about this:

We save some additional Info, e.g. into the filename (l234k5j2l34j234-gcc-3.0.1-kernel-2.4.10), so that after a compilerupdate (which is due to end of Oct, gcc-3.0.2), an simple perlscript can clean up the files from a specific compilerversion.

So, why not just delete all files when the new compiler arrives? Would work for me, but some want to keep two compilers at one (e.g. gcc-3.0.x and gcc-2.x), which can be pretty useful, since not all progs compile with the new gcc. Or with networked or shared cache, you can't just delete all files, but you CAN perhaps delete a specific compiler version.

Another example would be optimizer flags. When I sell my athlon and buy a whatever comes next, I have no use for cached athlon-optimized files.

What do you think?

Joachim 
+++++++++++++++++++++++++++++++++++++++++++++++
+              Joachim  Breitner              +
+             ===================             +
+  ma...@jo... | ICQ # 74513189  +
+  Homepage: http://www.joachim-breitner.de/  +
+ 07032/24774 | Ehbühl  33 | 71083 Herrenberg +
+++++++++++++++++++++++++++++++++++++++++++++++
+ If anything can go wrong, it will. (Murphy) +
+++++++++++++++++++++++++++++++++++++++++++++++
+ Linux, because:           +  Open  Minds.   +
+ Software is like Sex -     +  Open Sources. +
+ It's better when it's free! +  Open Future. +
+++++++++++++++++++++++++++++++++++++++++++++++
+ This message was written                    +
+           entirely with recycled electrons. +
+++++++++++++++++++++++++++++++++++++++++++++++
+ Crypt!    Meine PGP-Key ID: C0395780        +
+++++++++++++++++++++++++++++++++++++++++++++++