From owner-freebsd-questions@freebsd.org Tue Jul 14 00:27:28 2015 Return-Path: Delivered-To: freebsd-questions@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 0905499992B for ; Tue, 14 Jul 2015 00:27:28 +0000 (UTC) (envelope-from wiml@omnigroup.com) Received: from omnigroup.com (omnigroup.com [198.151.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "omnigroup.com", Issuer "The Omni Group CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E14AA1AD9 for ; Tue, 14 Jul 2015 00:27:27 +0000 (UTC) (envelope-from wiml@omnigroup.com) Received: from machamp.omnigroup.com (machamp.omnigroup.com [198.151.161.135]) by omnigroup.com (Postfix) with ESMTP id 06FF0241AD8C for ; Mon, 13 Jul 2015 17:19:12 -0700 (PDT) Received: from [10.4.3.119] (pfsense.omnigroup.com [198.151.161.131]) by machamp.omnigroup.com (Postfix) with ESMTPSA id 47A9111A28D0 for ; Mon, 13 Jul 2015 17:15:23 -0700 (PDT) From: Wim Lewis Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Naming a locally-built version of a package Message-Id: <37E1F657-243D-4F8F-A563-0C17B344D1B9@omnigroup.com> Date: Mon, 13 Jul 2015 17:19:09 -0700 To: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 00:27:28 -0000 Is there a particular recommended practice for naming a locally-built = package that is built with a local patch, or different configure = options, etc., so that it works well with the rest of the package = system, particularly dependencies and things? Ideally: let's say I'm building a custom version of Foo-1.3. I'd like to = name it such that: - Existing packages that require Foo will be satisfied by my patched = Foo - Local packages which require my patched Foo can specify a = dependency on it Less important but nice: - pkg audit will still recognize my Foo as Foo and inform me of = things I should know - The system won't suggest to "upgrade" my Foo to a non-patched Foo = of a later version=20 Is this (or a subset) possible with pkgng?