Date: Sun, 13 Jul 2014 14:02:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 185444] [NEW PORT] revive port games/wesnoth-devel Message-ID: <bug-185444-13-OCZxQMhvWl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-185444-13@https.bugs.freebsd.org/bugzilla/> References: <bug-185444-13@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=185444 --- Comment #4 from John Marino <marino@FreeBSD.org> --- 1) I've started the conversation with portmgr to establish a policy of -devel ports in general. It's not fun when a maintainer throws not one, but two ports on the heap when they give it up, and there are lots of problems with the -devel port is older than the real port. This is not about a single maintainer volunteering for a port -- it's a general burden multiplied potentially by 25,000 ports. And there's always a committer that has to deal with committing it, so there's a discussion that only ports that can really justify a -devel version will get it, especially given the new quarterly branches. There's also a discussion about port quality and using FreeBSD users as beta testers. for the specific case of wesnoth, it's probably best to get them to release again. There's no quality guarantee on a snapshot. 2) That comment was for the version hardy provided. 3) use a shar, but don't compress it or put it into a tar file. Just attach it do the PR. I think there's a 1MB size limit on attachments on bugzilla. -- 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-185444-13-OCZxQMhvWl>