Mail Archives: djgpp-workers/2000/12/06/12:57:39
> I was concerned about doing a make in a sandbox derived from a tree
> made with export. Since the "current" (i.e., last checkin) dates are
> not stamped on the exported sources, any part of the make that depended
Ah I see; I assumed that export would behave like checkout and use the
checkin timestamps.
> version, etc.). I was just anticipating possible problems.
That's never a bad thing. If only more programmers did that...
> I took your earlier advice and did a checkout, and that looks just fine
> to work with, except for the ubiquitous */cvs/* files. BTW, the
> instructions you gave above to strip the */cvs/* files out of a zipped
> tree use "zip" and "unzip" commands. Would you please tell me
> what/whose version of zip/unzip they are? Aliases for gzip/gunzip, I
Actually, no, just plain old InfoZip zip and unzip (like the
unzip386.exe on simtelnet).
> hope? If not, where can I get a copy?
www.freesoftware.com
or
ftp.freesoftware.com/pub/infozip
<potential patronising>
Basically
$ zip -9r foo bar
creates a foo.zip file containing the tree below bar, maximum
compression.
$ zip -d foo.zip */CVS/*
deletes all entries matching */CVS/* from the zip file (in bash you
may need to add single quotes, as the pattern should be expanded by
zip, not by the shell).
$ unzip foo.zip
simply unzips the lot (resulting in a tree similar to cvs export, but
with timestamps intact).
</potential patronising>
Of course, you could just use tar instead; it has similar options.
Or you could simply copy the tree (using cp -a), then use find to
trim the CVS dirs (find -type d -name CVS |xargs rm -rf).
Note that you may want to set the FNCASE envvar to 'y' before you run
zip/tar, to ensure files like NEWS or README don't get stored as
lowercase.
> Thanks for your kind instruction of this humble pupil, Tim. I really
> appreciate the clarity and simplicity of your replies.
Thanks for the excessive amounts of compliements :-)
- Raw text -