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

[Erik T. <er...@er...>]

hi

On Wed, Oct 17, 2001 at 03:26:21PM +0200, Josef Radinger wrote:
> Joachim Breitner wrote:
> > 
> > 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?
> 
> why not saving into different directories for different compilers?

just because it's additional complexity and of virtually no use.

think about it. you could do stuff like that everywhere in our
computing world: i'll just create some examples:

- the linux kernel could remove netscape from the buffer cache once
  galeon was installed by the user.

- web proxies could put every webpage in a separate directory so that
  the user could delete a directory of his choice to save some bytes
  of disk space.

- ... well. nothing more coming to my mind fast enough ;)

i just think that the cost-benefit ratio is very very bad for things
like that. and after all, you don't really want to manually tweak the
cache and erase files for old compilers or stuff like that. you just
want everything to silently work without thinking about it. so even if
you COULD remove the files generated from deleted compilers, you
probably wouldn't do it, would you?

cu
erik

-- 
Name:  Erik Thiele                                        \\\\
Email: er...@er...                                 o `QQ'_
WWW:   http://www.erikyyy.de/                              /   __8
                                                           '  `