From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Packages References: <87sn6yzq4n.fsf@photino.sid.rice.edu> <3225440905078102@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225484176996493@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Mar 2002 23:49:24 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1016495364 193.71.199.50 (Tue, 19 Mar 2002 00:49:24 MET) NNTP-Posting-Date: Tue, 19 Mar 2002 00:49:24 MET Xref: archiver1.google.com comp.lang.lisp:29478 * "Joe Marshall" | Unfortunately, at one place I worked the boss was insistent that we | always do a `clean build' before every check-in. But this is not a problem with Common Lisp, is it? :) I think making a clean build of the packages with a good defsystem, then loading them into a virgin image to dump a clean image should have been a satisfactory solution to your boss. If anyone has the kind of problem you have described, I think the proper answer is to teach them to use the implementation's ability to save the world and dump a new image, not to futz around with weird hacks. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.