Date: Tue, 05 Jun 2018 14:45:52 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 227600] porter's handbook: use of distinfo Message-ID: <bug-227600-7788-wC3zjUvm45@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227600-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-227600-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227600 --- Comment #4 from freebsd@dreamchaser.org --- (In reply to Tobias Kortkamp from comment #3) >> However, if one is updating a port, one needs to do the fetch before one= can >> run make makesum to produce an up-to-date version of distinfo. But one = can't >> do the fetch if a distinfo is lying around.=20 >=20 > This is incorrect. Let me try and clarify. >=20 > If you change PORTVERSION/DISTNAME/DISTFILES/... and then run `make > makesum` the new distfiles are fetched first and distinfo is replaced > with their checksums irregardless of what was in distinfo before. > You do *not* have to run `make fetch` first. >=20 > 'makesum' is the target you should use as a maintainer not 'fetch'. >=20 > Can you add a link to the section of the Porter's Handbook that you find > problematic? Ok, so what you're saying is one should not stepwise run make fetch and then make makesum; that's not clear from section 4.1, "How things work". 3.3 on building a new port implies the porter is responsible for updating distinfo by running make makesum after obtaining the source. Section 4.1 #1 is the part which could be expanded to explain more of how things work. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227600-7788-wC3zjUvm45>