1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
compilercache FAQ
*****************
Question overview
-----------------
1 ...... General
1.1 .... What is compilercache ?
1.2 .... Where do i get the current FAQ ?
1.3 .... You do not answer my emails !
1.4 .... There are no new releases. is compilercache dead ?
1.5 .... I want my features anyway ! what do i do ?
1.6 .... Are there RPM or DEB packages floating around ?
1.7 .... Why don't you build in all those cool features ?
1.8 .... Is there a compilercache mailinglist ?
2 ...... Cache Management
2.1 .... My cache grows too big, how do i shrink it ?
2.2 .... My cache directory has so many files, couldn't you split
it into subdirectories for speedup ?
2.3 .... Couldn't you compress the files in the cache directory ?
Answers to questions
--------------------
1.1 What is compilercache ?
see http://www.erikyyy.de/compilercache/
1.2 Where do i get the current FAQ ?
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/compilercache/faq/FAQ
1.3 You do not answer my emails !
I am sorry. Am not having very much time for compilercache. Most of
your emails need some time to think about them and often they have the
same kind of stuff inside that i already answered to someone else
before. That's why i created this FAQ. i hope it will improve the
situation.
1.4 There are no new releases. is compilercache dead ?
No. it is not dead. it is stable. There's a significant difference
here :) There seem to be no bugs in it. At least I get no bug
reports. But if I added all the new features that are suggested I am
absolutely sure there will be plenty of bug reports. I try to have the
program in a usable state. So far it seems to work for everyone.
1.5 I want my features anyway ! what do i do ?
The compilercache license is the GPL. You can do everything the GPL
permits. So for example you can create a new compilercache branch with
your features added. But I'd appreciate having a link to the original
compilercache on your website then :)
1.6 Are there RPM or DEB packages floating around ?
There are several people who did this. Ask on the mailinglist. I
myself am not involved in the development here. It is really easy to
have it installed by hand. this way you do not disturb the others with
your installation. If it is packaged as a RPM or DEB, then either it
has a global systemwide cache with write permissions for everyone
which is an enourmously big security risk! Other users can put wrong
compilation results in the cache and manipulate the software you are
installing on your machine! Or it does not do this and leaves every
user with his own cache directory. The next question is, is the PATH
variable systemwidely adopted to compilercache usage or does the user
have to set it by himself? If it is systemwidely set then remember
that some users have their PATH variables set from scratch in their
login scripts. So after all you end up in something like a selfdone
installation. it's just the compilercache script in some /usr/bin
path. I don't think RPM or DEB packages are that useful here. But I
may be wrong.
1.7 Why don't you build in all those cool features ?
you may also read 1.4 and 1.5. It's my philosophy. I like software
that just works and is both simple and stable. There are lots of small
problems like race conditions which will be added if not taking
extreme care when implementing the new stuff... I am afraid of making
mistakes there. I worked carefully on the current version so that it
doesn't have race conditions. At least i strongly hope so!
1.8 Is there a compilercache mailinglist ?
Yes there is!
http://lists.sourceforge.net/lists/listinfo/compilercache-general
2.1 My cache grows too big, how do i shrink it ?
Read 6. How do I clean all those Megabytes of Cache files ? in the
compilercache README file.
And please think about it. If your cache REALLY is sooooo enourmously
big, then go to a shop and buy some cheap 20 Gig harddrive. it will
never fill up and it's much easier to install that disk than to try to
change compilercache into using less diskspace! If erasing 10 day old
cache entries by cronjob does not erase enough, then you are probably
compiling really very very many things like complete linux
distributions on a daily basis and i think the investment in a new
harddrive could actually pay off. I prefer a working program and don't
like a buggy shellscript based cache management software instead ;-)
2.2 My cache directory has so many files, couldn't you split it into
subdirectories for speedup ?
you probably suggest something like:
/var/spool/compilercache/$USER/00 for all files starting with 00
/var/spool/compilercache/$USER/01 for all files starting with 01
like the way the squid web proxy cache does it.
i think such stuff is the job of the filesystem layer. a properly made
filesystem has no speed differences if you do it the current way or
the new way. it's just more code in the wrong place and more
possibilities for bugs.
2.3 Couldn't you compress the files in the cache directory ?
Read Question 2.2. The same argument holds here. If you want to have a
compressed cache, use a compressed filesystem for the cache directory.
|
