On Wed, November 19, 2014 4:50 pm, Post Fader wrote: > I'm trying to build/install a package that depends upon 50+ other > packages. One of these packages when downloaded and built does not have > correct LDFLAGS for my Mac OS 10.6 system. This is a 1 line change in the > makefile, and subsequently a manual build and install works just fine.
What package? > But I don't see a way to get fink to understand that my manual install has > happened and the dependency on this package has been satisfied, i.e., > using dpkg to de-select the file does no good (fink just says it's going > to use the de-selected package anyway, downloads it, clobbers my change, > and subsequently the build fails). By design, Fink always wipes the build directory because it's been designed to build identical packages no matter the underlying system. > Neither can I fink remove/purge a package which according to fink is not > yet installed. > > I finally searched under ./var to find all the "Depends:" lines, made > copies of the files, and then edited them to remove the dependency on the > package I want to skip. Now if I do You want the package description files in /sw/fink/dists/stable/main/finkinfo. These are the recipes that Fink follows to build a package. 'fink dumpinfo -finfofile <PKG>' will get you the file that deals with the package you're interested in. If the package has a patch file, it will be declared inside the <PKG>.info file > $ fink show-deps TARGET_PKG_TO_BUILD | grep -i MANUALLY_INSTALLED_PKG > > - the manually installed package is not listed. > > Yet when I try to do "fink install TARGET_PKG_TO_BUILD" fink nonetheless > still eventually lists the manually installed package as a dependency, > tries to download it, and subsequently the build fails. I did a fink scan > packages, cleanup, but fink still insists that package I don't want it to > build has to be built. > > So i next tried patching the downloaded source tar archive to include the > Makefile change, but because this changes the checksum, after running fink > install again, even the override option (4) to use the > "incomplete/damaged" package fails. Once again, it downloads the original > package, clobbers my change, and the build subsequently fails. > > I can understand that for a "turn key" solution this stringent approach to > not allowing people to tamper/patch builds could be a good thing. I am > not as familiar with Debian package tools as I am with rpm and yum, but it > seems to me that fink should have an option to let you change dependencies > on as yet uninstalled packages including use your own custom *local* > packages and/or override dependencies as you may need to. Fink is not Debian. We use the debian tools to do .deb file handling, but the actual build system is external to that. Once you find the .info file for your package, copy it (and any PatchFiles that belong to it) to /sw/fink/dists/local/main/finkinfo and edit there as you wish. Bump the revision field by 1, and then Fink will determine that yours is newer than what's in the distro. Selfupdate never touches the local directory, so you don't have to worry about losing your changes. Hanspeter -- More agile than a turtle, stronger than a mouse, nobler than a lettuce ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Fink-beginners mailing list Fink-beginners@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
