How about using the .patch file to do just that? On 6/11/03 12:31 PM, "Avram Dorfman" <[EMAIL PROTECTED]> wrote:
> Hello, > > I recently had a problem where fink couldn't install a package b/c the > package was failing build. I was able to fix the problem (and email the > maintainer w/ the fix ;-). However, the procedure I used to intervene > into fink's ways felt like a bigger hack than necessary. I'm wondering > if there's a simpler way. > > Here's what I did: > > 1) Installed the package, let it fail > 2) found the tarball, and expanded it to a temp directory > 3) hacked it, and re-tar'd it on top of the old one (huh-huh, he said > 'retard') > 4) re-installed it, and selected 4 to ignore the mismatched checksum > > It seems like there should be a way to just hack the already-expanded > source tree, and tell fink to do it's thing from that. Instead, fink > insists on stomping the left-over source tree with something fresh from > the tarball, and thus the tarball steps are needed. > > -Avram > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Fink-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/fink-users > -- Alexander K. Hansen Associate Research Scientist, Columbia University visiting MIT Plasma Science and Fusion Center Levitated Dipole Experiment 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
