Also might want to punt this towards [EMAIL PROTECTED] --Noah
On Oct 9, 2007, at 6:38 PM, J.M. Maurer wrote: > On Tue, 2007-10-09 at 18:30 -0400, Eben Eliason wrote: >> On 10/9/07, J.M. Maurer <[EMAIL PROTECTED]> wrote: >>> On Tue, 2007-10-09 at 23:52 +0200, Marco Pesenti Gritti wrote: >>>> On 10/9/07, Eben Eliason <[EMAIL PROTECTED]> wrote: > [] >>>> I think the c++ component (libabiword) is currently installed in >>>> the system. >>> >>> Exactly; libabiword is not part of the Write bundle. We could do >>> that >>> ofcourse, but then other applications can't benefit from the >>> libabiword >>> code (such as a Develop activity for example). >> >> No, I see the complication. That code definitely belongs separate >> from Write. I think the thread is just titled wrong, as this is a >> policy concern for "system software" and not for individual >> activities. > > The title reflects the initial problem I was facing. Given the current > solution direction, the title is indeed wrong. Feel free to open a new > thread :) > > Marc > > _______________________________________________ > Sugar mailing list > [email protected] > http://lists.laptop.org/listinfo/sugar > _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
