Alexander Hansen wrote: [] > Every package has a slightly different build process, so unless > somebody else has done it already, you're going to have to play around > with the package yourself. Maybe start with 'configure --help' in the > net-snmp build directory. If there is an option like --enable-python, > and if so you can put that in the ConfigureParams line of the net-snmp > package description file.
To elaborate on this, if you want to play with configure options in a Fink package, it is a good idea to copy the file(s), in this case net-snmp-unified.info and net-snmp-unified.patch, from /sw/fink/dists/unstable/main/finkinfo/net/ to /sw/fink/dists/local/main/finkinfo/ (create the latter directory if it doesn't exist) and then start modifying the copy. In order to be sure that it is your copy that is going to be used, it is best to raise the revision number, for example by replacing the line Revision: 2 by Revision: 2.0 Everything you can do inside the *.info file is described in the Fink packaging documentation at <http://www.finkproject.org/doc/packaging/index.php> You would probably start by removing the --without-python-modules from the ConfigureParams field and then watch what happens. As Alex suggests, you will also need to query the configure script in /sw/src/fink.build/net-snmp-unified-5.4.1-2.0/net-snmp-5.4.1/ about possible options, like --with-python-modules. -- Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
