Date: Wed, 20 May 2009 09:34:51 -0400 From: Sean McAfee <smcafee@collaborativefusion.com> To: "Frank J. Laszlo" <laszlof@freebsd.org> Cc: "Philip M. Gollucci" <pgollucci@p6m7g8.com>, freebsd-ports@freebsd.org, Vladimir Ermakov <samflanker@gmail.com> Subject: Re: New port: sysutils/megacli waiting to commit Message-ID: <4A1406FB.7020502@collaborativefusion.com> In-Reply-To: <4A13F48D.9040009@freebsd.org> References: <4A13AB59.9060002@gmail.com> <4A13C3E6.20209@p6m7g8.com> <4A13F48D.9040009@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank J. Laszlo wrote: > Philip M. Gollucci wrote: >> Vladimir Ermakov wrote: >> >>> Hi, all. >>> please appreciate my port *megacli* >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=133655 >>> >> >> Is that different from this the port, is it an update? >> >> Path: /usr/ports/sysutils/linux-megacli >> >> > > Since the megacli application now has a native binary, should be not > DEPRICATE the linux version? > > Regards, > Frank Laszlo Probably not. I noted this when I originally filed the PR for linux-megacli2, but the 1.x, 2.x, and 4.x versions support dramatically different hardware lines. As an example, this native version is 4.x and does not support the Dell PERC5. IMO, linux-megacli, linux-megacli2, and megacli should all exist as independent ports. -- Sean McAfee System Engineer Collaborative Fusion, Inc. smcafee@collaborativefusion.com 412-422-3463 x 4025 5849 Forbes Avenue Pittsburgh, PA 15217 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ****************************************************************
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A1406FB.7020502>