I've noticed an inconsistency in the 'make clean' behavior.
# --- MakeMaker clean section:
# Delete temporary files but do not touch installed files. We don't delete
# the Makefile here so a later make realclean still has a makefile to use.
clean ::
-rm -rf ./blib $(MAKE_APERL_FILE) $(INST_ARCHAUTODIR)/extralibs.all perlmain.c
tmon.out mon.out core core.*perl.*.? *perl.core so_locations pm_to_blib *$(OBJ_EXT)
*$(LIB_EXT) perl.exe perl perl$(EXE_EXT) $(BOOTSTRAP) $(BASEEXT).bso $(BASEEXT).def
lib$(BASEEXT).def $(BASEEXT).exp $(BASEEXT).x
-mv Makefile Makefile.old $(DEV_NULL)
While the clean target doesn't *delete* the Makefile, it does rename
it to Makefile.old. This contradicts the comment. realclean just
deletes Makefile.old.
On VMS the Makefile (well, Descrip.mms) is left alone in the clean
target.
So which is right? Put another way, is there any reason 'make clean'
should touch the Makefile?
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
We have returned to claim the pyramids.
