Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Johnny Hughes
On 05/30/2014 12:50 PM, Eugene Vilensky wrote: On Fri, May 30, 2014 at 12:09 PM, Jim Perrin jper...@centos.org wrote: 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

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Johnny Hughes
On 05/30/2014 01:58 PM, Les Mikesell wrote: On Fri, May 30, 2014 at 12:09 PM, Jim Perrin jper...@centos.org 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

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Johnny Hughes
On 05/30/2014 12:50 PM, Eugene Vilensky wrote: On Fri, May 30, 2014 at 12:09 PM, Jim Perrin jper...@centos.org wrote: 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

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Les Mikesell
On Mon, Jun 2, 2014 at 6:55 AM, Johnny Hughes joh...@centos.org wrote: On 05/30/2014 01:58 PM, Les Mikesell wrote: 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

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Jim Perrin
On 06/02/2014 07:47 AM, Les Mikesell wrote: On Mon, Jun 2, 2014 at 6:55 AM, Johnny Hughes joh...@centos.org wrote: On 05/30/2014 01:58 PM, Les Mikesell wrote: Is yum supposed to track the dependencies separately? That is, if an EPEL package requires some other package (expected with the

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Les Mikesell
On Mon, Jun 2, 2014 at 8:53 AM, Jim Perrin jper...@centos.org wrote: That seems pretty dangerous if the packages replace standard or EPEL libraries/components. I'd have expected them to have some sort of namespace concept for dependencies to keep the sets of packages completely

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Johnny Hughes
On 06/02/2014 10:06 AM, Les Mikesell wrote: On Mon, Jun 2, 2014 at 8:53 AM, Jim Perrin jper...@centos.org wrote: That seems pretty dangerous if the packages replace standard or EPEL libraries/components. I'd have expected them to have some sort of namespace concept for dependencies to keep

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Les Mikesell
On Mon, Jun 2, 2014 at 10:15 AM, Johnny Hughes joh...@centos.org wrote: I consider this a bug, as the SCL's should be self-contained. We'd need to see if this occurs upstream as well, and then file a bug there if so. There's really a bigger issue of how EPEL is supposed to fit in the world

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Jim Perrin
On 06/02/2014 10:06 AM, Les Mikesell wrote: There's really a bigger issue of how EPEL is supposed to fit in the world of 'other' repositories. What should happen when centosplus/extras has a same-named package? Other 3rd parties?

Re: [CentOS] nodejs, epel, SCL

2014-06-02 Thread Jim Perrin
Top posting: Seems someone's already filed this as a bug. You can keep an eye on the progress via - https://bugzilla.redhat.com/show_bug.cgi?id=1042879 Similar bug impacting SSSD - https://bugzilla.redhat.com/show_bug.cgi?id=1089090 On 05/30/2014 10:18 AM, Eugene Vilensky wrote: Hello,

[CentOS] nodejs, epel, SCL

2014-05-30 Thread Eugene Vilensky
Hello, ​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?

Re: [CentOS] nodejs, epel, SCL

2014-05-30 Thread SilverTip257
On Fri, May 30, 2014 at 11:18 AM, Eugene Vilensky evilen...@gmail.com wrote: Hello, ​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

Re: [CentOS] nodejs, epel, SCL

2014-05-30 Thread Jim Perrin
On 05/30/2014 10:18 AM, Eugene Vilensky wrote: Hello, ​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

Re: [CentOS] nodejs, epel, SCL

2014-05-30 Thread Eugene Vilensky
On Fri, May 30, 2014 at 12:09 PM, Jim Perrin jper...@centos.org wrote: 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

Re: [CentOS] nodejs, epel, SCL

2014-05-30 Thread Les Mikesell
On Fri, May 30, 2014 at 12:09 PM, Jim Perrin jper...@centos.org 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