From owner-freebsd-ports-bugs@freebsd.org  Thu Dec  3 10:17:14 2015
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DBD4A3E799
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu,  3 Dec 2015 10:17:14 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1A39A1DCB
 for <freebsd-ports-bugs@FreeBSD.org>; Thu,  3 Dec 2015 10:17:14 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tB3AHDMx007644
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 3 Dec 2015 10:17:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 204577] [NEW MODULE] Mk/Uses/nodejs.mk Framework for NodeJS
 projects/ports
Date: Thu, 03 Dec 2015 10:17:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: needs-patch, needs-qa
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ports@toco-domains.de
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-204577-13-o22qjJ5Hgh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204577-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-204577-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2015 10:17:14 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204577

--- Comment #22 from Torsten Z=C3=BChlsdorff <ports@toco-domains.de> ---
(In reply to yuri from comment #18)

> I chose an approach to make the separate FreeBSD ports for large apps tha=
t=20
> end-users care about.

I understand your approach, but there are also ports depending on single sm=
all
libs. deskutils/ladon for example could be unbroken when having async, glob,
mkdirp and yargs in tree.

While large apps are great for end-users we should not forget there is a
growing number of tools which npm-dependencies.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=