Date: Sun, 03 Jun 2018 19:49:22 +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-ZZoJTSGmb5@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 #2 from freebsd@dreamchaser.org --- You're correct in that the message clearly states that distinfo is out of d= ate. 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. A user can easily think "I know it's out of date, I'm trying to fetch the file and generate an up to date version!" The issue is not with the failure message; the issue is with the general description of the fetch phase in the Porter's Handbook. It would be helpf= ul if the Handbook indicated the fetch itself will not succeed if a distinfo is lying around which does not match the file being fetched. It is not at all clear that a mis-matched distinfo will cause a fetch to fail, particularly since distinfo is not required to be there to perform a fetch, and cannot be generated until after the fetch is done. One could also make the message a little clearer, such as: =3D> Either /hd2/home/garya/Computing/ports/graphics/nufraw/distinfo is out= of date, or =3D> nufraw-0.41.tar.gz is spelled incorrectly. =3D> If distinfo is out of date, delete it before attempting to fetch. --=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-ZZoJTSGmb5>