No registered users in community xowiki
in last 10 minutes
in last 10 minutes
Re: [Xotcl] XOTcl packages
From: Stefan Sobernig <stefan.sobernig_at_wu-wien.ac.at>
Date: Sat, 04 Apr 2009 14:50:09 +0200
(sorry for double posting, forgot about digest mode)
Jeff,
> Message: 2
> Date: Fri, 03 Apr 2009 11:29:34 -0700
> From: Jeff Hobbs <jeffh_at_activestate.com>
> Subject: Re: [Xotcl] XOTcl packages
> To: Victor Mayevski <vitick_at_gmail.com>
> Cc: xotcl_at_alice.wu-wien.ac.at
> Message-ID: <49D6558E.200_at_activestate.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 03/04/2009 11:24 AM, Victor Mayevski wrote:
>> I really like that XOTcl is being included with ActiveState
>> distribution, and even updates via teacup are working. But there is
>> one issue - why is it that the rest of XOTcl packages (comm,
>> serializer etc) are not being included?
>
> The teapot is designed for individual packages (though they can have
> dependencies). In building, it goes through the usual configure / make
> / install steps. XOTcl only packages up the core library when it does
> that. The other packages would be best handled separately somehow.
Couldn't teacup provide the "--with-all=yes" configure flag so that the
accompanying infrastructure is included?
//stefan
Date: Sat, 04 Apr 2009 14:50:09 +0200
(sorry for double posting, forgot about digest mode)
Jeff,
> Message: 2
> Date: Fri, 03 Apr 2009 11:29:34 -0700
> From: Jeff Hobbs <jeffh_at_activestate.com>
> Subject: Re: [Xotcl] XOTcl packages
> To: Victor Mayevski <vitick_at_gmail.com>
> Cc: xotcl_at_alice.wu-wien.ac.at
> Message-ID: <49D6558E.200_at_activestate.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 03/04/2009 11:24 AM, Victor Mayevski wrote:
>> I really like that XOTcl is being included with ActiveState
>> distribution, and even updates via teacup are working. But there is
>> one issue - why is it that the rest of XOTcl packages (comm,
>> serializer etc) are not being included?
>
> The teapot is designed for individual packages (though they can have
> dependencies). In building, it goes through the usual configure / make
> / install steps. XOTcl only packages up the core library when it does
> that. The other packages would be best handled separately somehow.
Couldn't teacup provide the "--with-all=yes" configure flag so that the
accompanying infrastructure is included?
//stefan