From owner-freebsd-ports@freebsd.org Tue Oct 18 05:58:32 2016 Return-Path: Delivered-To: freebsd-ports@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 52550C16377 for ; Tue, 18 Oct 2016 05:58:32 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 40006234 for ; Tue, 18 Oct 2016 05:58:32 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3F666C16376; Tue, 18 Oct 2016 05:58:32 +0000 (UTC) Delivered-To: ports@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 3F12FC16375 for ; Tue, 18 Oct 2016 05:58:32 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F03F233 for ; Tue, 18 Oct 2016 05:58:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u9I5wLAw013605 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 17 Oct 2016 22:58:24 -0700 (PDT) (envelope-from julian@freebsd.org) To: "ports@FreeBSD.org" From: Julian Elischer Subject: private ports and pkgs versioning Message-ID: <1cba6ef9-89af-c3b8-48df-0cbdc8499b6c@freebsd.org> Date: Tue, 18 Oct 2016 13:58:15 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 05:58:32 -0000 Is there a standard way of naming a pkg that is locally compiled (maybe with a different set of options, or a local patch) so that it doesn't get confused with generic ports that are from freeBSD.org? I want to use mostly standard pkgs but need to compile a few myself (this can't be an uncommon requirement). How can I name my variant pkgs so the the pkg program (and ports) can still know that it is a satisfactory supplier of prerequisite components? e.g. if a pkg wants a specific rev of libxml2 how much does it use of the name libxml2-2.9.2_2 ? Can (should) I add stuff after the '_'? If I do will it still recognise my pkg file and if I do are there any rules regarding *WHAT* I can put there. lastly is there somewhere I should be looking to read all this information rather than pestering the mailing list? What I'd like to have is my own depot with something like: === libsmi-0.4.8_1.txz libxcb-1.11.1.txz libxml2-2.9.2_2-mumble.3.txz lsof-4.88,8.txz lsof-4.90.b,8.txz m4-1.4.17_1,1.txz === where 'mumble.3' is a locally defined addition, but all the rest of the pkgs are straight from pkg.freebsd.org, (or at least compile in default form). This "kind-of" works, but the rules of play are not defined anyhere I have read, so I don't know if it's going to suddenly fail one day. Also it's be really nice if there were a variable I could set to "mumble.3" so that I don't have to do a manual rename, because between the time that the package is made and it is renamed there is a 'misnamed' package sitting around acting as a potential source of confusion. thanks, Julian