From owner-freebsd-questions@freebsd.org Tue Jul 14 22:34: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 B7A959A24FE for ; Tue, 14 Jul 2015 22:34:21 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 893AF1F5F for ; Tue, 14 Jul 2015 22:34:21 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-207-98-175-216.knology.net [207.98.175.216] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t6EMYEvc008248 for ; Tue, 14 Jul 2015 17:34:14 -0500 Message-ID: <55A58E65.9050000@hiwaay.net> Date: Tue, 14 Jul 2015 17:40:28 -0453 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Naming a locally-built version of a package References: <6C655B93-082B-4782-872B-F411BA722F85@omnigroup.com> <55A57BDA.50901@FreeBSD.org> In-Reply-To: <55A57BDA.50901@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 22:34:21 -0000 On 07/14/15 16:21, Matthew Seaman wrote: > On 14/07/2015 19:23, Wim Lewis wrote: > >> Is $PORTREVISION a good place to note the presence and revision of >> my local changes (e.g., as "o3" since only one letter is allowed)? Is pkg's >> version-number-comparison behavior documented somewhere--- how it orders >> alphabetics and what it does with the VERSION and REVISION parts of the >> version string? > You can test the ordering of two version strings using 'pkg version -t' > > Note however, if your modified version is Foo-1.0.0.o1 and an update is > pulled in from upstream then the regular port version Foo-1.0.1 will > supersede your locally modified version. You might find it more > effective to use an epoch number instead: Foo-1.0.0;1 which will always > sort higher than anything without the ';1' bit. Beware though that once > you've added an epoch number you can never remove it. > >> Would it be reasonable to treat local patches as options? That is, my >> local variant of Foo-1.3_5 would still be named Foo-1.3_5.o3, but >> would have the option SPIFFY_LOCAL_PATCH. I've noticed that pkg >> records the build options of packages but it's not clear to me what >> it does with that information (if anything; is this just there to >> support future behavior that hasn't been implemented yet?). > pkg(8) tracks the option settings almost entirely for documentation > purposes at the moment. They don't feature in what the solver is doing > currently -- but keep watching this space. You can add your local > changes as new options if you like, but I don't think it's going to have > quite the effect you're hoping it will. Hmmmm .... If it is indeed aware of pkg options, could it decide to favor pkg's w/ other-than-std. options, on the assumption that the user was locally overriding something on his/her own judgment ? $0.02, no more, no less .... > > There are a number of changes which are going to hit the ports in the near > future, particularly 'FLAVOURS' which you might find interesting. > FLAVOURS is all about compiling certain ports several times with > alternate dependency choices, eg. 'Foo with mysql' vs. 'Foo with > postgresql' vs 'Foo with sqlite' > > Cheers, > > Matthew > > -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.