Date: Fri, 29 Jun 2018 18:08:53 +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-1cV1o5yjNO@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 Kurt Jaeger <pi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pi@FreeBSD.org --- Comment #6 from Kurt Jaeger <pi@FreeBSD.org> --- section 3.3 explains for quick ports, how to generate the distinfo. section 4.1 is verbose, but does not really mention make makesum. section 4.2 says to get the source somehow, but doesn't mention make makesu= m, either. If I write a new port, I normally use cd /usr/ports/category port create <newport> using ports-mgmt/porttools. Then I try to get the skeleton port Makefile to fetch it's distfiles. If that works, I can use make makesum. If we replace 4.2 with a rough description like that above, would that be helpful ? Is it allowed to depend on ports-mgmt/porttools in the porters handbook or is it frowned upon ? --=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-1cV1o5yjNO>