Hi Jan, On Mon, Jan 26, 2009 at 3:28 PM, Jan Ciger <[email protected]> wrote: > You are not taking into account that 64bit systems are far less > prevalent than 32bit ones, even though most machines sold in the last > two years are capable of running 64bit code. So your assertion does not > really carry that much weight here.
Sigh. I know what I see when I pull down source code packages, build and install them. I've used 64bit linux builds solidly for the past four years. When I say the majority of such packages are installing to /ur/local/lib rather than /usr/local/lib64 you really need to take this on board rather than dismissing it. The situation is far far from clear cut like you like to make out and frankly it's frustrating having to waste time repeating my experience of 3rd party software that just doesn't chime with your assertions. > It makes sense in a way - if there is nothing installed, there is no > need for the path, unlike /usr/lib*. It is the responsibility of the > software being installed to set itself up appropriately. Um... is it a good thing to expect 3rd party software to have to modify system files or user paths just to be found when they are being installed in what one claims to be a "standard" place. IMHO, If it's a standard directory then there shouldn't be any need to modify LD_LIBRARY_PATH or ld.so.conf files, if you are modifying these files then it kinda suggests that you have non standard configuration. Is /usr/local/lib* a standard place to put libs or not? I'm very curious to what other distributions do w.r.t ld.so.conf and /usr/local/lib*. > Mandriva has/used to have version 1.0 in the contrib repositories (i.e. > community supported package, not company supported), packaged by Stefan > van der Eijk <stefan at mandriva dot org> and later by Per Øyvind > Karlsen <pkarlsen at mandriva dot com>. However, if I recall correctly, > Per has stopped working on anything Mandriva-related due to personal > reasons and has left Mandriva. The package is essentially orphaned right > now. > > You can get the source RPM package from here: > http://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/devel/cooker/SRPMS/contrib/release/OpenSceneGraph-1.0.0-1mdk.src.rpm I don't scale well in terms of contacting all the maintainers of the different distro's, so would appreciate others chasing up the details of the various distro's and what we need to do to fit in better with them. If needs be we can populate the OpenSceneGraph/packaging directory with my platform specific scripts/config files. This has always been may plan for this directory. > That includes at least the spec file which could be used as a start to > build a newer package. Do you have link to just the spec file or the file you could just send directly? > You could also post a packaging request to the > Cooker mailing list > (http://wiki.mandriva.com/en/Development/Mailinglists), it is possible > that someone will pick it up and make a package. Any volunteers to do this :-) >> Perhaps another solution would be to have CMake check where the >> installed library is on the search path or not, and if not to produce >> a suggestion of how to add it to the path. > > Isn't this the case already? I recall that the build used to produce a > message at the end that you should do so. Did this change after > introducing CMake build? To be honest, I didn't actually notice it > disappearing, but I am rebuilding OSG using a set of scripts and didn't > really look for this any more :) I'm afraid there is no messages other a big loooong list of files being installed. Another job for one us to do before OSG-2.8... Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
