Hi Tracey, Tracey Emery writes: > Could you explain > the need for the conflict? Shouldn't it be okay to have both ngspice and > libngspice installed at the same time with the removal of the includes > and shares?
libngspice and the new ngspice revision, yes. But think about the case where someone has the old ngspice package installed, without running pkg_add -U, and then tries to install libngspice. That's why the @conflict marker lists only ngspice with a version less than p0 (REVISION = 0), and also why the ngspice PLIST doesn't need a @conflict marker (we can't retroactively add a @conflict to old copies of ngspice that have the headers, and new ngspice doesn't conflict with anything). -- Anthony J. Bentley
