| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: perl pmda package install problems |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Mon, 5 Oct 2015 17:27:20 -0400 |
| Cc: | "'pcp developers'" <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <5612EA0C.7070208@xxxxxxxxxxxxxxxx> |
| References: | <00df01d0fd5b$36fb3b30$a4f1b190$@internode.on.net> <y0msi5su02y.fsf@xxxxxxxx> <5612D6B1.8040509@xxxxxxxxxxxxxxxx> <20151005203541.GB32129@xxxxxxxxxx> <5612EA0C.7070208@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi - > As Tadej pointed out in a related post, we're already using the > perl(...) syntax. > > The problem for (me) is on 30+ machines with different software > installations, I have to answer the question ... > > - which package that I have not already installed delivers the Perl > LWP::UserAgent module? How about # yum install 'perl(LWP::UserAgent)' or local yum equivalent? That's the point of the virtual resource name, it doesn't matter what the low-level rpm name is. > and then repeat for every Perl/Python/library/executable dependency ... Assuming you're building/installing binaries other than distro packages yeah. If you do have the distro binaries, then the package-install tooling should be able to pull in those dependencies (once portably specified). - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: perl pmda package install problems, Ken McDonell |
|---|---|
| Next by Date: | Re: [pcp] pmcd restart race condition, Nathan Scott |
| Previous by Thread: | Re: perl pmda package install problems, Ken McDonell |
| Next by Thread: | Re: perl pmda package install problems, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |