On Fri, May 30, 2014 at 12:09 PM, Jim Perrin <jperrin@xxxxxxxxxx> wrote:
>
>> With SCL and epel repositories enabled, some dependencies for the package
>> name 'nodejs' get satisfied with libs from SCL which are placed in paths
>> that are not part of my user's environment. Is there a method to make sure
>> that nodeJS from epel dependencies are only satisfied from epel?
>
> EPEL is self-reliant. Nothing in EPEL will depend on another other than
> Base/Updates. You need to check which repo you're installing the package
> from, and be careful with the package name itself. There shouldn't be
> duplicate names.
>
> In your example, the nodejs package is coming from SCL, so you would
> need to use the scl tools to enable that utility (which then
> appropriately updates your user's environment)
Is yum supposed to track the dependencies separately? That is, if an
EPEL package requires some other package (expected with the stock
paths), can an SCL package fulfill that dependency even though it will
be installed in a location that won't work?
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
