Date: Fri, 05 Oct 2018 20:55:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 231814] [patch] Update comms/owfs to 3.2p2 Message-ID: <bug-231814-7788-eUChXi53Nu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231814-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-231814-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=3D231814 --- Comment #4 from Johan Str=C3=B6m <johan@stromnet.se> --- Comment on attachment 197795 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D197795 owfs 3.1p1 -> 3.2p3 update patch Thanks, OWFS specific stuff looks good to me, but I think current MASTER_SI= TES will not be approved by porters. First of all, remove sourceforge, the project have left Sourceforge in favo= ur of Github, and further releases won't show up there. Second, in bsd.sites.mk there is a DEV_WARNING about using github.com in MASTER_SITES, so I suspect this will be problematic? Not sure how to exactly use it, but the following seems to work with the current port:=20 USE_GITHUB=3Dyes GH_TAGNAME=3Dv${DISTVERSION} Although it doesn't download the release tar.gz but rather tar.gz snapshot = from the repo.. The distfile gets namde owfs-owfs-3.1p1-v3.1p1_GH0.tar.gz and putting that in distinfo seems to build fine... Not sure whats most appropriate, perhaps some port manager can aid with assistance here? Will mark the patch as maint approved and we might get some input! --=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-231814-7788-eUChXi53Nu>