Steve Baur wrote:
> This causes problems for me since there are packages I don't
want
> to install and I don't want to compile at all (they are checked
> out, however, since it's simpler to call `cvs co' only once, at the
> toplevel directory).
Do a `make distclean; cd ..; cvs release -d <unwanted-package>' to get
rid of the source of unwanted packages. `cvs update' does not [re]create
directories, so you should be able to continue updating when necessary.
Yes, but this means that I'll have to checkout manually any new
package that appears in the tree, right ? Usually, I just `cvs update -Pd' at
the toplevel. If I keep on doing this, the effect of the `cvs release' command
will be lost.
> Actually, since I never could checkout skk properly, the make
process
> bombs out on this one and I have to modify the SUBDIRS variable of
> its Makefile by hand to remove it from the make process.
? Can you provide any more details?
This is a problem I add for ages. Each time I check out skk, the
command fails saying something like "could not allocate 32 bytes". I talked
with Jareth about this, and he advised me NOT to use cvs 1.10.2. But I never
took the time to compile another version than the one we have installed here.
Can you delete the source as > described above, then do `cvs
update -d skk'
to get good source?
cvs [server aborted]: out of memory; can not allocate 41 bytes
cvs release: unable to release `skk'
Something else is required for doing a partial bytecompile. Would
you
consider a marker file sufficient? For example, if you could touch a
`.nobuild' file in the packages you never want to build, would that
work for you?
Sure.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19