On Jan 9, 8:34 am, Volker Braun <vbraun.n...@gmail.com> wrote: > I say we don't do anything special. Ccache will use the default ~/.ccache > or CCACHE_DIR if set. Why muck around with it if there is a perfectly fine > configuration system in place already? > > [vbraun@volker-desktop ~]$ du -sh ~/.ccache/ > 44G /home/vbraun/.ccache/
Indeed, and *warn people about it*. On many multi-user systems, you wouldn't want to use $HOME for such high-volume stuff, because it's expensive storage (because of backups) and slow (because it's networked). Using the standard gives people tools to avoid doing so (i.e., set $CCACHE_DIR or make .ccache a symlink). Incidentally, how does ccache operate if $HOME/.ccache is shared between computers with different architectures and operating system versions/compiler versions? Does it notice and avoid that? Does it notice when difference are small enough that both machines would produce identical code? [I know ccache's specification promises that its presence doesn't change code produced, but is a shared .ccache within their assumptions?] -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
