
On Wednesday, October 15, uk1o@rz.uni-karlsruhe.de wrote:
Another way were patching the third party program's Makefile accordingly. We should introduce a patches-${OPSYS} directory having precedence before the patches directory of a port. Thus we could maintain our special patches for ports which need them while continuing to use the FreeBSD ports where they work out of the box. I see now that this is already implemented in <bsd.port.mk>, so we could just USE that.
I've already made a similar message to the ports list. It was shot down. But maybe now that we see the "trouble" with the current setup, we can re-evaluate that. Personally, I think we could share 95% of the ports stuff between open/freebsd, but it would be nice to have the ability to fix things in a local cvs tree, without having to wait for the fix to go through channels. --Toby. *----------------------------------------------------------------------------* | Tobias Weingartner | Email: weingart@BrandonU.Ca | Need a Unix sys-admin? | | 6B-1137 Lorne Ave. |-----------------------------| Send E-Mail for resume, | | Brandon, Canada | Unix Guru? Admin, Sys-Prgmr | and other details... | |----------------------------------------------------------------------------| | %SYSTEM-F-ANARCHISM, The operating system has been overthrown | *----------------------------------------------------------------------------*