Hi Ralf,
I've followed some of this thread. From my perspective:
* I'm okay what whatever is decided, as long as "maintainer-clean"
semantics do not change. New semantics -> new name, just like
the way any other interface change should work
* I don't particularly care for the "autogen.sh" name for a boot-
strap script. GNOME adopted the name after I suggested using
my tool for some repetitive tasks.
* if you are going to add new names, then the inverse of a
"foo" step should likely be named "foo-clean", pre-existing
tradition excepted.
* since running a bootstrap script is not part of the make process,
it seems less than obvious to me that a make target should
undo the bootstrap.
* How about having autoreconf (aka "bootstrap") take an option:
autoreconf --clean
bootstrap --clean
I have my own script that traverses the hierarchy and removes any
file or directory not under version control. That's pretty
effective for me. :)
Regards - Bruce
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Autogen-users mailing list
Autogen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/autogen-users
