Wesley Shields wrote:
On Thu, Jun 26, 2008 at 08:38:00AM -0700, Jo Rhett wrote:
The current maintainer has indicated that he is holding up the quagga
0.99.10 port until an unknown time when the TCP MD5 checksum patches
are again working in the tree. I don't think that this is the right
thing to do, as the TCP MD5 checksums are not necessary for the vast
majority of installations, and DO NOT work with a GENERIC kernel.
I'd like to request that the port be split into two ports -- one with
a stock quagga installation, and the other with the MD5 checksum
patches, due to the instability and constant work on said patches
making the port unstable. (and being unavailable right now holds up
access to a major bugfix line)
You already have the option for TCPMD5 being on or off (off by default).
The solution in my mind is not two separate ports, but what is used now:
OPTIONS. If an option is broken why not mark it as such until it can be
addressed? If the patches become a workable (yet still experimental)
option the BROKEN line can be removed. The port can still keep using
newer versions while the patches are being developed.
I agree. Two ports are overkill for only TCPMD5 option. And it should
not be a show stopper for the port update.
--
Dixi.
Sem.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
