From owner-freebsd-ports-bugs@freebsd.org  Mon Nov 30 20:44:12 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 4DB29A3D439
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Mon, 30 Nov 2015 20:44:12 +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 3A3C819C8
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 30 Nov 2015 20:44:12 +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 tAUKiCNr099020
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 30 Nov 2015 20:44:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 204904] Making CKSUMFILES more flexible by allowing USES
 clauses to add files there
Date: Mon, 30 Nov 2015 20:44:12 +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: 
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: <bug-204904-13-OdnyWzec8J@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204904-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-204904-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Mon, 30 Nov 2015 20:44:12 -0000

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

--- Comment #4 from yuri@rawbw.com ---
npm first pre-builds locally, then places the result into another, separate
hosting location, and then during port build they just download and unpack it.

There are many NodeJS projects, you can't make everybody do this manually. And
the way I suggested with USES=nodejs circumvents the problem, and builds it all
in a close to normal way. Please note that the fetch is really a fancy fetch,
it doesn't compile anything.

This makes it a bit difficult to implement USES=nodejs, but easy to make many
ports based on it.

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