From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Mitchell To: craig@jcb-sc.com Cc: patrick@mail.boxsoft.com, egcs@egcs.cygnus.com, craig@jcb-sc.com Subject: Re: why does g77 build? Date: Fri, 30 Apr 1999 23:15:00 -0000 Message-ID: <199904251522.IAA13751@adsl-206-170-148-33.dsl.snfc21.pacbell.net> References: <199904250430.VAA07112@3eye.boxsoft.com> <19990425125723.8671.qmail@deer> X-SW-Source: 1999-04n/msg00880.html Message-ID: <19990430231500.G6b3HdFY6JGW2CkdAx50d1MjDXBhv-5s99IRmRgXCDY@z> >>>>> "craig" == craig writes: >> But since I'm replying to this post I'll just ask if it would >> be too terribly hard to have the ./configure setup a Makefile >> that would "spit" out a shell script (uninstall.sh) after 'make >> install' completes that would have a list similar to this: >> >> rm -f $(prefix)/egcs-stuff-that-got-installed-1 rm -f >> $(prefix)/egcs-stuff-that-got-installed-2 ... rm -f >> $(prefix)/egcs-stuff-that-got-installed-n >> >> Basically an rm list of all the files it installed. So then >> the user wouldn't need to keep the src-tree for uninstalling it >> for the next release. Just keep the script to run at a later >> time. craig> I'm 100% in favor of that. Wish all software worked that craig> way. But it is, as you noticed when looking at the source, craig> something that would require a nearly complete redesign of craig> how installations are done, from the top (the GNU approach) craig> on down. craig> In the meantime, a feasible solution is to always configure craig> to install into a unique tree, then substitute "rm -fr craig> $(unique-prefix)" for running the shell script you and I craig> want spat out by the install. (I use this approach to craig> manage development snapshots, multiple FSF/EGCS releases of craig> gcc, etc. It works quite well.) I find GNU stow very useful for this kind of thing. It's available on prep. -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com