-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Robert Osfield wrote: > HI Jan, > So for the past half dozen emails you've been saying that > /usr/local/lib64 is the "standard", but... there are also all these > other standards... You were asking about /usr/local/lib vs. /usr/local/lib64, not where and how does 3rd party software get installed in general. > Given all these difference ts there a common system for ld.so.conf.d > that we could leverage? i.e my suggestion of installing a > openscenegraph.conf that points to the installed directory would only > work if we knew that there was a standard place to put this file. > This does sound like a long shot. If the system is using the ld.so.conf.d directory, it is likely always /etc/ld.so.conf.d (it is part of glibc which is common for most distros). However, that directory is not really obligatory, so your machine may or may not have it, in the latter case using only file /etc/ld.so.conf for the list of directories. > The question then is... how to we make it easier for these downstream > package maintainers. > > It's also a two process - the package maintainers are typically rather > too disconnected from upstream development. I realise the is hard > given that maintainers are probably trying to cover many different > packages. While there are many hundreds of distro's there are ten of > thousands of packages. To me it'd make sense to leverage the original > software communities like ours to take responsibility for such package > management as at least we have more people in our Well, that would be a question for the maintainers and you would probably get as many different answers as there are maintainers. I agree with your notion that the community could (and should) help, but being a decent packager is a huge job. I have built a few packages before, but I would hesitate trying to package something as a big as OSG in a way that would pass Mandriva's muster for inclusion in the distro. I can try it, though. Usually, the following helps to make a package without too much effort: making sure that the application builds on the targeted distro with minimal patching, has no hardwired paths anywhere (i.e. follows --prefix with autoconf or similar, uses something like /usr/bin/install for deploying files), does not require much beyond 'configure; make; make install' (or similar) to build and does not have lot of dependencies. That should have the most bases covered. One part which is often troublesome are plugins - things that are optional, but have to be selected at compile time. Essentially it would require one package per plugin unless one is willing to pull in all the dependencies for all plugins on every install, even if not needing all plugins. Every distro has different policies with regards to such cases. Regards, Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFJff/9n11XseNj94gRAv7YAJ0UPHkIwh5e5VTrjSzOt7zHIHDxSACcC2i8 aSGS/59HEa/wU54tM0LjVyU= =uR1j -----END PGP SIGNATURE----- _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
