On Sat, Jul 5, 2008 at 7:12 PM, Tom Russo <[EMAIL PROTECTED]> wrote: > On Sat, Jul 05, 2008 at 12:02:07PM -0700, we recorded a bogon-computron > collision of the <[EMAIL PROTECTED]> flavor, containing: >> On Sat, 5 Jul 2008, Tom Russo wrote: >> >> > Adding configure command line options is always necessary to deal with >> > nonstandard installs. Peppering the configure script with tricks to look >> > everywhere that might have the desired files is unmaintainable and often >> > breaks. Look at the mess we have for BDB --- it tries all manner of crazy >> > things to find db headers, and often screws up, all because no two installs >> > of BDB seem to be consistent. >> >> Rgr. BDB: Another of nemesis of ours, and of other projects! >> >> If the /usr/include/geotiff/ directory becomes commonplace later I'd >> advocate adding it to our autoconf scripts. > > But at this point it isn't --- geotiff's install doesn't do that itself, the > Ubuntu package maintainer must have decided to isolate the headers for > some reason, and just did it. > > A note to the maintainer might be in order. Some packages do that, but it > is not the norm. I'm not sure that many packages that use libgeotiff are > going > to expect its headers to be in nonstandard locations.
Remember this geotiff/Ubuntu package discussion from July? Recent experience with Mepis 7.0, AntiX 7.2, and DreamLinux 3.0 has found that the geotiff dev package is coming from Debian. So Ubuntu, the 3 distros above, Debian, and (I expect) virtually all of the other Debian based Linux distro's have the same geotiff package in their repo's. This one may be widespread enough to warrant changing the configure script to look in /usr/include/geotiff. Mepis, Antix, and Dreamlinux also, by the way, have access to what I believe is the same Xastir 1.9x binary that has been available to Ubuntu. Regards, Lee - K5DAT Murphy, TX _______________________________________________ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
