On May 1, 2:14 am, "Rakhesh Sasidharan" wrote:
> On Sat, 30 Apr 2011 23:21 -0700, "Sans" wrote:
> > On May 1, 4:59 am, Matthew Black wrote:
> > > You can put a requires in the file resource
>
> > > require => Package["packagename"]
>
> > > then it will install the package first then put in the
On 1.5.2011 10:15, Sans wrote:
> 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 ldco
Thanks Rakhesh, looking into it. Cheers!!
On May 1, 8:14 am, "Rakhesh Sasidharan" wrote:
>
> In that case my suggestion of yesterday should do the trick -
>
> Have a Exec resource with a command to link the files above, but which
> runs only if the file does not already exist. Something along th
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 ->
f
On Sat, 30 Apr 2011 23:21 -0700, "Sans" wrote:
> On May 1, 4:59 am, Matthew Black wrote:
> > You can put a requires in the file resource
> >
> > require => Package["packagename"]
> >
> > then it will install the package first then put in the symlink.
> >
> That not what I actually want. I just s
On May 1, 4:59 am, Matthew Black wrote:
> You can put a requires in the file resource
>
> require => Package["packagename"]
>
> then it will install the package first then put in the symlink.
>
That not what I actually want. I just simply want: if the package
already installed, create the sym-link
