From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E584813877A for ; Wed, 20 Aug 2014 18:35:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E9E65E080B; Wed, 20 Aug 2014 18:35:05 +0000 (UTC) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 08D96E07D0 for ; Wed, 20 Aug 2014 18:35:04 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id u57so8201536wes.24 for ; Wed, 20 Aug 2014 11:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=L03NZGn7YRHM0dPEQApsxB2Inlt17SXBMKonRibWtaI=; b=Z6WpUxnoiM//NVKv3Ch1V4ABXiuBrXUpzWMh0Rx3mDSPezkqf1x45YIQJI4wIrs3rd jmOzXXNgVJ/eFsqiDxQ8mITyTg77Gf/a+XOT7J7gcfbl1huSeNVQpE3bYbQQOizW5SEl go5KCdq/rQXQCC2a9VZeR8V93IbEl1i/UoeyVa7d6dQcY565Lj/iOzF2hdOgfjPdV+r0 cEPVqJSKyRFEs5MUtOeUmzy1Do6FW7ZbWkXklFOqXt4nVe5+4XiFlxfYgcjHJxcIwP5K Me7PnslR3wXiG8dq2Dn8UYbHQ2jAJ506FAoVD8x/6sG2Hp5D0c1amVP1tu+2CaKMVTsr UrKg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.194.103.41 with SMTP id ft9mr13673572wjb.93.1408559703588; Wed, 20 Aug 2014 11:35:03 -0700 (PDT) Received: by 10.194.237.133 with HTTP; Wed, 20 Aug 2014 11:35:03 -0700 (PDT) In-Reply-To: References: <20140820084808.5f78c624@archtester.homenetwork> Date: Wed, 20 Aug 2014 14:35:03 -0400 Message-ID: Subject: Re: [gentoo-dev] Fw: reviewboard and its bugs From: Tim Boudreau To: Gentoo Developers Content-Type: multipart/alternative; boundary=089e0102d912c70932050113dc1b X-Archives-Salt: 59a04a1a-7481-4ca0-aa63-4be1ab79a1cd X-Archives-Hash: f4bbe14f066ee1480d67c7d9b70a5efd --089e0102d912c70932050113dc1b Content-Type: text/plain; charset=UTF-8 On Wed, Aug 20, 2014 at 11:08 AM, Jesus Rivero (Neurogeek) < neurogeek@gentoo.org> wrote: > I originally responded to another thread. Here is what I said: > < > I gave this a try some time ago and was bummed down by some things. I dont > like nodejs enough, and npm devs seems to not care about centrally/globally > installed packages. There are some npm packages that have to be modified so > they can work when globally installed and it gets boring after a while. npm > packages tend to be really small so one package can have a really high > number of deps. > For NodeJS, the first-class thing is web applications, and as far as their concerned, the "best practice" is, if your application uses a library, it should have its own copy of it. And, for web applications, that *does* guarantee that you know what version of everything you're deploying, and allows an application to have dependencies which themselves have conflicting dependencies - which helps ensure deployment is uncomplicated and you know what you're deploying. However, globally installed packages are supported, and are increasingly important as people discover NodeJS is useful for things that are not web-application related. So it seems like something that's not going away, and sooner or later package managers will have to deal with it. > If anybody is interested in this, check out my repo with npm packages[0] > and a really simple g-npm tool[1] to generate ebuilds for them. These tools > might be outdated cause I don't use nodejs anymore and I dont care much > about it. > g-npm looks interesting. -Tim --089e0102d912c70932050113dc1b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, Aug 20, 2014 at 11:08 AM, Jesus Rivero (Neurogeek) &l= t;neurogeek@gento= o.org> wrote:
I originally responde= d to another thread. Here is what I said:
<
I gave this a try some time ago and was bummed down by some= things. I dont like nodejs enough, and npm devs seems to not care about ce= ntrally/globally installed packages. There are some npm packages that have = to be modified so they can work when globally installed and it gets boring = after a while. npm packages tend to be really small so one package can have= a really high number of deps.=C2=A0

For NodeJS, the first-class thing is= web applications, and as far as their concerned, the "best practice&q= uot; is, if your application uses a library, it should have its own copy of= it. And, for web applications, that *does* guarantee that you know what ve= rsion of everything you're deploying, and allows an application to have= dependencies which themselves have conflicting dependencies - which helps = ensure deployment is uncomplicated and you know what you're deploying.<= /div>

However, globally installed packages are supported, and= are increasingly important as people discover NodeJS is useful for things = that are not web-application related. =C2=A0So it seems like something that= 's not going away, and sooner or later package managers will have to de= al with it.
=C2=A0
If anybody is interested in this, chec= k out my repo with npm packages[0] and a really simple g-npm tool[1] to gen= erate ebuilds for them. These tools might be outdated cause I don't use= nodejs anymore and I dont care much about it.

g-npm looks interesting.
<= br>
-Tim

--089e0102d912c70932050113dc1b--