Date: Thu, 11 Dec 2014 09:33:58 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 195797] [revive port] Patch to fix port /usr/ports/mail/synonym Message-ID: <bug-195797-13-NjVivqzOgQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-195797-13@https.bugs.freebsd.org/bugzilla/> References: <bug-195797-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=195797 --- Comment #3 from tedm@mittelstaedt.us --- I presumed the original port maintainer would have been automatically emailed and might have eventually got back to it once he saw the change was so trivial. I guess when the port was marked broken the original maintainer's email address was struck from the port. OK whatever. I didn't know we were doing that now. This one built fine under 9.2 6 months ago and has worked ever since. Back in the "olden days" in FreeBSD we had a principle that if you made trivial unnecessary changes in the code that broke other stuff that you fixed what you broke. Changing USE_GMAKE variable to the USES variable must have broken hundreds if not thousands of ports and there seems no justification for it other than someone's sense of aesthetics. I suppose whoever did it is real proud of themselves as it has obviously killed many orphaned ports that otherwise worked fine but were on autopilot with maintainers out to lunch. Good Job! No wonder people go to Linux. So be it. Filing this was purely a hand out to whoever might have just updated to a new system and had this break. You might consider that syndrome is in the ports distro included with the 9.3-RELEASE ISO so anyone installing Ports off that instead of sucking the current ports tree down is going to get this port and when they try to build it they will run into this nonsense. It would have saved me an hour if this bug report had been in the system. If someone else wants to adopt this orphan at least they will know what is needed to fix it. I am not interested in going through the formal process of reviving and adopting this just to make a single line change. It worked fine for me when it was on autopilot and it works fine today on 9.3. The next time I build a server that needs it I'll just build it manually and screw fooling with ports. You guys are too busy breaking things in there anyway. Incidentally, it makes no difference if -Wno-pointer-sign is there or not since that just suppresses a warning anyway, and the compiler does the Right Thing in either case. -- 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-195797-13-NjVivqzOgQ>