SCIENTIFIC-LINUX-USERS Archives

May 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Sommerseth <[log in to unmask]>
Reply To:
David Sommerseth <[log in to unmask]>
Date:
Sat, 30 May 2015 09:17:40 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (14 lines)
On 30 May 2015 02:00:46 CEST, Tini <[log in to unmask]> wrote:
>i forgot to ask, how do i get around the 'file dependency' problem? 
>should i just add all of the libraries? :-D 


As others have suggested, using 'yum localinstall' is the preferred approach, for two reasons. First of all that the dependencies are taken care of - or it will tell you which dependencies can't be found, and that yum will not complain about rpm having been used outside of yum.

If you want to add these external packages to more machines, it may be more convenient to create your own repository server.  All you need is a web server where you can upload all your own packages and run createrepo in that directory. Then you add your own repo file in /etc/yum.repos.d with the baseurl variable pointing to your own server and path to your packages. Once that is in place, yum install will do the rest.  The advantage here is that when you upload updated packages to your web server and run createrepo again, all your boxes gets updated automatically next time the yum update job runs (unless you've disabled the auto update, then running 'yum update' or the gnome/kde update applet will do the job).

--
kind regards,

David Sommerseth

ATOM RSS1 RSS2