From owner-freebsd-ports-bugs@freebsd.org Mon Dec 14 21:11:17 2015 Return-Path: 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 B8D2EA4303D for ; Mon, 14 Dec 2015 21:11:17 +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 A9B2714DA for ; Mon, 14 Dec 2015 21:11:17 +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 tBELBHG8021057 for ; Mon, 14 Dec 2015 21:11:17 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: Mon, 14 Dec 2015 21:11:17 +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: yuri@rawbw.com 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2015 21:11:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204577 --- Comment #32 from yuri@rawbw.com --- (In reply to Torsten Z=C3=BChlsdorff from comment #31) nodejs.mk fetches everything needed for the port during the fetch phase, th= en packages port with all dependencies so that this port always works the same way. Build doesn't require the network access. We use shrinkwrap feature th= at npm provides and recommends to use to freeze the dependencies. I just don't see how can individual ports be created for all dependencies. = This is a very large amount of work to maintain them. Also please note that different projects can require different versions. How can having a single version on ports suit such requirement? Also if the older distfile disappea= rs on the source, this will break the individual ports the same way. So besides saving the space having them doesn't provide any advantage in NodeJS case. I currently have 5 ports working, and looking at some other, larger project= s to make ports for. Making ports for simple projects is trivial, finding larger projects that can also be built on FreeBSD seems to be a challenge (few of = the ones that I found require large external C++ projects to work that weren't ported or require qt-5.5). --=20 You are receiving this mail because: You are on the CC list for the bug.=