Hi, That's not what I want. I just want to be able to recompile everything and then install everything in one step. That would make the development cycle much easier. Mathias pretty much understood what I wanted to do (skip the unpacking & patching steps).
I am beginning to wonder if I am misunderstanding the whole model of porting and developing unix packages using fink. How does everyone else do the change->compile->test->change->compile->test->release cycle with fink?? Adam on 3/17/03 8:32 AM, Max Horn at [EMAIL PROTECTED] wrote: > Am Montag, 17.03.03 um 10:40 Uhr schrieb mathias meyer: > >> to correct myself: >> >> of course another 'fink rebuild foo' will delete the source directory. >> if you want fink only to do parts of >> unpacking/patching/compiling/installing you would have to edit >> Engine.pm. this is NOT really recommended but i tell you anyway... >> > In fact I would strongly discourage of doing that. If you do it, we do > not want to see any problem reports on it. > > If you want to just avoid having to recompile everything when a single > source line has changed, then you should go and install ccache and > ccache-default > > > Max > > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Fink-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
