Date: Thu, 07 Dec 2023 07:02:38 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 272553] security/p5-Net-SSLeay fails to build Message-ID: <bug-272553-14331-DlDxSYvwhP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272553-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-272553-14331@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=3D272553 --- Comment #14 from Felix Palmen <zirias@freebsd.org> --- (In reply to Dave Hayes from comment #13) > BTW I imported a -tagged- developer release. If I understand this correct= ly, a > git tag doesn't move. Also, if you look at the repo, this was tagged 10 m= onths > ago and hasn't moved. It's technically possible to move a tag, but it *should* not move, so this wasn't the point. I called it "moving" because this project seems to publish multiple "revisions" of the same developer release. To do it correctly, you= 'd have to include this revision number as well in DISTVERSION. But my main concern was indeed just the fact that this is labelled a *developer* release. It's certainly ok to use that for a port, but there sh= ould be a reason to prefer it over the latest *stable* release. I'd rather avoid such decisions on ports I don't maintain myself, unless I can present a str= ong reason... --=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-272553-14331-DlDxSYvwhP>