From owner-freebsd-questions@freebsd.org Tue Jul 14 16:05:21 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 27B549A1647 for ; Tue, 14 Jul 2015 16:05:21 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-ig0-f193.google.com (mail-ig0-f193.google.com [209.85.213.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F15D09F6 for ; Tue, 14 Jul 2015 16:05:20 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by igbqa2 with SMTP id qa2so1353237igb.0 for ; Tue, 14 Jul 2015 09:05:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=references:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-type; bh=YjhqPFXPHotp6ZTONAEiAwAefp3ltfMtyfoSCg/gp9Y=; b=RLCFQQNijGBQNVffhpDt9wswUN+5w7F5afY8cQW9hPwzguJrDHOglCmPlyaYP5ciQ0 fZ7q5gvIr2kkpK+8yFj3IuusoC6WJ9JZq2azENuRdU8gLSKjBqYfSBw8UDiBrhaAI3aR NmdqLVha6lSyFzoQWshrMr4XnLdFvmGNQDyJvwlgoLwYstkYl4iuE/LYJ0AAtcfAHL4s LfUkB0uuZQjM/zXL7KYBtEb3+z3Jf1mMI1N/l3Kq8TsiK/pXF83RqoIrXua2LgIOIih6 E3xefEDXXsStKo0fSe8XwIOpllRsV4Mn4THK8v+oJTwhdM+w9KmWCRpxuN4IUMBN7zOn odsg== X-Received: by 10.107.137.154 with SMTP id t26mr53219463ioi.13.1436882152666; Tue, 14 Jul 2015 06:55:52 -0700 (PDT) Received: from WorkBox.Home.gmail.com (75-168-176-141.mpls.qwest.net. [75.168.176.141]) by smtp.gmail.com with ESMTPSA id ji7sm1616352igb.2.2015.07.14.06.55.50 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jul 2015 06:55:51 -0700 (PDT) References: <37E1F657-243D-4F8F-A563-0C17B344D1B9@omnigroup.com> From: Brandon J. Wandersee To: Wim Lewis Cc: freebsd-questions@freebsd.org Subject: Re: Naming a locally-built version of a package In-reply-to: <37E1F657-243D-4F8F-A563-0C17B344D1B9@omnigroup.com> Date: Tue, 14 Jul 2015 08:55:49 -0500 Message-ID: <86oajevo62.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain 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 16:05:21 -0000 Wim Lewis writes: > 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 > > Is this (or a subset) possible with pkgng? > If you're just build a small number of packages (maybe 5 or fewer), use `pkg lock`. If you're build lots of custom packages, set up a personal package repository. pkg(8) is capable of distinguishing between different builds of a package via a) origin, and b) custom build-time options--no need to change the name. -- ================================================================= :: Brandon Wandersee :: :: brandon.wandersee@gmail.com :: ================================================================== 'A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.' - Douglas Adams ==================================================================