Date: Sat, 16 Aug 2014 18:27:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 184203] [NEW PORT] net/motsognir: an ANSI C gopher server Message-ID: <bug-184203-13-jv9aOBzA9W@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-184203-13@https.bugs.freebsd.org/bugzilla/> References: <bug-184203-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=184203 --- Comment #14 from John Marino <marino@FreeBSD.org> --- (In reply to Mateusz Viste from comment #13) > Hi, > > I fear most of the things you listed are black magic to me. > > I installed the "poudriere" system, but it only says "Error: Unable to find > /usr/local/share/poudriere/../../etc/poudriere.conf", so I obviously missed > something obvious. Yes, you have to configure it, build a jail, and install a ports tree. It's like a computer with an OS and a mostly empty hard-driver. It works "out of the box" but there's not much to do until you install other stuff. Basically your issue is you don't know know to how to use poudriere. moving on... > "make check-plist" says: "make: don't know how to make check-plist. Stop", > which I am not sure is abnormal, since I have the same result on all > existing ports I tested. Maybe because of this: "NO_STAGE= yes" > Tinderbox wasn't able to install on my system, failing to fetch some > required file: Poudriere > tinderbox. If you are going to start from scratch, stick with poudriere and forget tinderbox. > Portlint is one thing that I was able to use out of the box. It generated a > few fatal errors at first, but I fixed them all by fiddling with the > Makefile. Now it only says this: > > root@bsd:/usr/ports/net/motsognir # portlint > WARN: Makefile: Consider adding STAGE support. ^^^^^^^^^^^^^^^^ that's not warning, that FATAL It means your portlink is out of date too, you should update that. > I attached here the latest version of my ("un-poudriered") port, just in > case someone, some time in the future, would like to take it to the next > level. I am quite confident now that porting stuff to BSD should be done > only by people used to it (or smarter than me, maybe). I will get back to > writing C, it's way easier than BSD porting, apparently :) There are hundreds of people that do porting, it's not that exclusive a club or really any kind of special talent... > Anyway, as of now, I think it will be best you just reject this bug report, > as its unlikely to evolve in any near future. I am really sorry for having > wasted your time on this. If it's unstaged (and it is) and there's no update coming, I have no choice but to close the PR. You didn't waste my time. Thanks, John -- 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-184203-13-jv9aOBzA9W>