From owner-freebsd-questions@freebsd.org Mon Jan 11 10:28:48 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2223E4D4573 for ; Mon, 11 Jan 2021 10:28:48 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from cp160176.hpdns.net (cp160176.hpdns.net [91.238.160.176]) (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 4DDqgL6H4Lz3GNS for ; Mon, 11 Jan 2021 10:28:46 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=milibyte.co.uk; s=default; h=Content-Type:Content-Transfer-Encoding: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=nCL+MMP1N23sHXQ8SR5G5MF6Rnu99fEEkdAFL1YZTBs=; b=bvjJ3F2SqobDCQOja94rlZh1ij yjAIEIEwX9rmrbBf8/ze0kGHRHmxe9pAo82U5VslezImlsRfDxdK84QxW+d89MfNu4+sSy6hBLgdN ZAekuHjpX5zCzGPcXOmAbKDd85POGANv4uKKzehBQeKH4fFAaH0vAYm92+KQIXnLs2J+wTL+fED/O uVnGO7FJ5SPFuPITh7PEsJuFJw9rJyC/nZAQcLMCWp3cruyPgt2/25h6ZuaFK049Znin6nFgUopew YwurxaTR40wyp+q/Ph0SyUqHFU+G78flV3cfdC3o29OdeQnMQ3wbQt4t7Je8F2HJnas7wfsI0tYZ2 XqaaXcJA==; Received: from 82-71-56-121.dsl.in-addr.zen.co.uk ([82.71.56.121]:36403 helo=curlew.milibyte.co.uk) by cp160176.hpdns.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kyuR9-000i4f-I7 for freebsd-questions@freebsd.org; Mon, 11 Jan 2021 10:28:35 +0000 Received: from [127.0.0.1] (helo=curlew.localnet) by curlew.milibyte.co.uk with esmtp (Exim 4.94) (envelope-from ) id 1kyuR9-0007Cc-IK for freebsd-questions@freebsd.org; Mon, 11 Jan 2021 10:28:35 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Subject: Re: github ports Date: Mon, 11 Jan 2021 10:28:10 +0000 Message-ID: <2005774.cYikG52F1y@curlew> In-Reply-To: References: <20210110133605.6538dfd5@dismail.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-YourOrg-MailScanner-Information: Please contact the ISP for more information X-YourOrg-MailScanner-ID: 1kyuR9-000i4f-I7 X-YourOrg-MailScanner: Found to be clean X-YourOrg-MailScanner-SpamCheck: X-YourOrg-MailScanner-From: jmc-freebsd2@milibyte.co.uk X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp160176.hpdns.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - milibyte.co.uk X-Get-Message-Sender-Via: cp160176.hpdns.net: authenticated_id: mailpool@milibyte.co.uk X-Authenticated-Sender: cp160176.hpdns.net: mailpool@milibyte.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Rspamd-Queue-Id: 4DDqgL6H4Lz3GNS X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=milibyte.co.uk header.s=default header.b=bvjJ3F2S; dmarc=none; spf=pass (mx1.freebsd.org: domain of jmc-freebsd2@milibyte.co.uk designates 91.238.160.176 as permitted sender) smtp.mailfrom=jmc-freebsd2@milibyte.co.uk X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; HAS_X_SOURCE(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[milibyte.co.uk:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; HAS_X_ANTIABUSE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[91.238.160.176:from]; CTE_CASE(0.50)[]; ASN(0.00)[asn:12703, ipnet:91.238.160.0/22, country:GB]; HAS_X_AS(0.00)[mailpool@milibyte.co.uk]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[milibyte.co.uk:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[milibyte.co.uk]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[91.238.160.176:from:127.0.2.255]; HAS_X_GMSV(0.00)[mailpool@milibyte.co.uk]; MID_RHS_NOT_FQDN(0.50)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2021 10:28:48 -0000 On Sunday, 10 January 2021 18:49:43 GMT Vasily Postnicov wrote: > There is no "git update" command > > At first delete the old port tree, then from /usr do > "git clone git://github.com/freebsd/freebsd-ports ports". From /usr/ports > run "make index" or "make fetchindex". > > To update the tree do "git pull" from /usr/ports and then again "make > fetchindex" I usually build a small number of packages from ports because I need different options. It doesn't seem justifiable to install and run poudriere to handle such a small number of ports. What I do is to use pkg upgrade to update the rest of my packages and then sync my ports tree with the revision which was used to build the current packages. This avoids the risk of incompatibilities when mixing ports and packages. This process would be much easier if there was some mechanism built into the pkg system to easily determine the revision number of ports corresponding to the last run of pkg upgrade. In the absence of such a feature I find the svn revision by checking the latest revision on the build server's webpage. For my version of FreeBSD (12.2 on AMD64), this is currently http:// beefy6.nyi.freebsd.org/ but I've occasionally had problems in the past when things have moved to a different server. Is there any chance that when we move over to using git for ports there could be a convenient way of identifying the git revision number of the commit corresponding to the time when pkg upgrade was last run.? -- Mike Clarke