X-Original-To: alpine-aports@mail.alpinelinux.org Delivered-To: alpine-aports@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id 12316DC7E6A for ; Mon, 11 Apr 2016 13:33:01 +0000 (UTC) Received: from newmail.tetrasec.net (unknown [74.117.189.117]) by mail.alpinelinux.org (Postfix) with ESMTP id 53FA4DC7E4D for ; Mon, 11 Apr 2016 13:33:00 +0000 (UTC) Received: from ncopa-desktop.alpinelinux.org (229.63.200.37.customer.cdi.no [37.200.63.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by newmail.tetrasec.net (Postfix) with ESMTPSA id 3B9115A155C; Mon, 11 Apr 2016 13:32:59 +0000 (GMT) Date: Mon, 11 Apr 2016 15:32:54 +0200 From: Natanael Copa To: Jose-Luis Rivas Cc: =?ISO-8859-1?B?U/ZyZW4=?= Tempel , alpine-aports@lists.alpinelinux.org Subject: Re: [alpine-aports] [PATCH] testing/nodejs-stable: new aport Message-ID: <20160411153254.35e8c830@ncopa-desktop.alpinelinux.org> In-Reply-To: <20160309212446.GA1396@riseup.net> References: <20160229190942.GA6571@riseup.net> <20160309155213.GA9700@calcium.lan> <20160309212446.GA1396@riseup.net> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; x86_64-alpine-linux-musl) X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP On Wed, 9 Mar 2016 16:24:46 -0500 Jose-Luis Rivas wrote: > On 09/03/16, 04:52pm, S=F6ren Tempel wrote: > > On 29.02.16, Jose-Luis Rivas wrote: =20 > > > We have the LTS release on main/nodejs and the new features are being > > > added to the stable release which is at v5.7.0 (vs v4.3.1 for LTS). > > >=20 > > > There's a replace against nodejs so there's no conflicts when someone > > > tries to install them together. =20 > >=20 > > Do we really want to maintain two different versions of nodejs? > > Personally I don't think that it is a good idea to maintain both the > > newest and the LTS version of a software in the official repositories. > > The only package that I know of where we do this currently is firefox > > and I don't think that it has worked very well in the past with firefox. > > =20 >=20 > They do differ quite a lot and most production units are using > nodejs-lts (the one we have already as plain nodejs) yet the newer > features are being added to nodejs-stable. While some things may fail on > nodejs-stable everything will work on nodejs-lts. >=20 > That's the reason why I see having the two versions of it would be > useful. nodejs-stable is not necessarily the newest, since lts keeps > getting updates, but not new features. (Yet, newer releases tend to be > synced between both versions) >=20 I think I am ok with maintaining both. I wonder if we want call them 'nodejs' and 'nodejs-stable' though. If i would see those variants I would believe that nodejs-stable would be the mode suitable for production, while in this case the lts is what you'd want for that. Maybe we all them nodejs4 and nodejs5? Other ideas? -nc --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org ---