Date: Tue, 31 Oct 2006 13:26:37 -0800 (PST) From: mjacob@freebsd.org To: Scott Long <scottl@samsco.org> Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN changes-next set of changes ready for review Message-ID: <20061031132438.G21918@ns1.feral.com> In-Reply-To: <4547B9D1.6060201@samsco.org> References: <7579f7fb0610281854l3ec600d7kf0a2cdf20fdcb838@mail.gmail.com> <7579f7fb0610282210p59de2123g379f0d4069bd1e42@mail.gmail.com> <45443C7F.5040508@samsco.org> <7579f7fb0610300801x4650cb3fgb93f662fbf7b4213@mail.gmail.com> <20061031115204.Y21918@ns1.feral.com> <4547B9D1.6060201@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> >> /usr/ports/audio/cdparanoia >> /usr/ports/audio/sound-juicer >> /usr/ports/audio/xmcd >> /usr/ports/emulators/mtools >> /usr/ports/misc/mtx >> /usr/ports/multimedia/k9copy >> >> I *think* based upon scanning them that only cdparanoia would have to >> *really* be recompiled- in fact, it just an XPT_PATH_INQ, so it might even >> get away from having to be recompiled. >> >> Any glaring omissions? >> >> -matt >> > > I think that there are some GNOME and KDE apps that also might be > affected. You can always pass a patch off to the ports team (portmgr) > and ask them to do a trial run with it. They are always very open to > that; better to have everything fixed ahead of time than to deal with > things suddenly breaking. The sound-juicer stuff and k9copy are part of GNOME. I mailed portmgr, but it strikes me that all I need to do is get through a complete build cycle in ports myself- if possible. This should leave enough work stuff around that I can grep for CAM in source files and see if things would break. Jeez, what a lotta work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061031132438.G21918>