Hi Steven and vagn, I almost forgot about ldconfig, I had a look now and ldconfig doesn't appear to be working in this particular case. It's conventional for the so_name to be the name+major version of the library (although, not universally done), so ldconfig will create a link like "foo.so.1 -> foo.so.1.1.1" and "foo.so.1.1 -> foo.so.1.1.1" but *not* foo.so -> foo.so.1.1.1, as far as I understand. It should be created manually, I suppose. Cheers!!
On May 1, 6:03 am, Steven Acres <[email protected]> wrote: > [ .... ] > > As vagn noted, the package manager should be handling this, there most > likely is a valid reason it isn't creating those links (aside from 'bugs'). > And if you're sure you want to customize a pkg., re-roll the pkg. You'll > thank yourself later, guaranteed. > > -- > Cheers, > > Steven > ----------------------- > Steven Acres > UNIX/Linux System Administrator -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
