[lively-kernel] Local installation of Lively Core from Github: some notes, questions, and errors

[Milan Zimmermann]

On Wed, Feb 29, 2012 at 6:19 PM, Conrad Calmez
<conrad.calmez at student.hpi.uni-potsdam.de> wrote:
> Hello,
>
> today I sat down and had a look at the installation process of Lively
> Kernel on Debian and Mac OS X.
> I reworked the installation notes and the Apache configurations for
> Linux.  I also added the Apache cofiguration (as well as the
> corresponding description) to my GitHub fork for the LivelyKernel
> repository.
> I just saw that the markdown is not perfect, but it is still readable.
> I created a pull request to get my changes in
> https://github.com/rksm/LivelyKernel.
>
> @Milan: If you want to have a look at that go to
> https://github.com/calmez/LivelyKernel  (esp. INSTALL.md)
> (I am really sorry, that I am maybe too late with my help)

Hi Conrad:

This is great, thanks, I will not have time to get back to it fully
until weekend anyway, any notes and experience help. I started to
script the whole installation process in a shell script which is
slowing me down, repeatability is good but it is slow to achieve and
the process hurts...

To all:

I have a general question: If I decide to keep PartsBin in an actual
SVN repo for versioning: Let's say I first bootstrap PartsBin using
the script that uses

   Config.rootPath = 'http://lively-kernel.org/repository/webwerkstatt/'
   $world.openPartItem("BootstrapParts", "PartsBin/Tools")

Then, let's say I work for a while. save some things locally, etc,
then decide to get PartsBin *updates* from
http://lively-kernel.org/repository/webwerkstatt/ again.

Is there a way to do that that anyone here uses? [I think it was
answered as negative, but wanted to check, thanks.  (At the same time
it can  likely be done by merging from  a read-only mirror master or
similar but surely must be a pain). Apart from that, is there perhaps
a plan to base the wiki versioning on Git rather then SVN?]

thanks
milan
>
> If there are any open questions to my changes, I will be happy to answer them.
>
>
> -- Conrad
>
> On Wed, Feb 29, 2012 at 5:54 AM, Milan Zimmermann
> <milan.zimmermann at gmail.com> wrote:
>> Jens, Fabian, Robert:
>>
>> Thanks all for your comments - this was really helpful. I will mark
>> this thread for my next round of installation. Below I just summarize
>> topics and responses, more or less for myself:
>>
>> - the save problem is not lively related, just WebDAV likely my
>> permission problem to check into
>> - the format error can be fixed by pulling the bootstrap as Jens did
>> - authentication is done through regular Apache digest config (just
>> need to set it up right), no interaction with Lively
>> - PartsBin items can be served either via SVN repo or SVN working copy
>> as explained (I will likely use working copy for now so I can update
>> easily and not worry about local versions for now)
>> - LivelyKernel is served from git repo (=working copy) so this should
>> be locally versioned as is
>>
>> I will report here any further successes or questions,
>>
>> Thanks again
>>
>> Milan
>>
>> On Tue, Feb 28, 2012 at 2:27 PM, Robert Krahn
>> <robert.krahn at hpi.uni-potsdam.de> wrote:
>>> a) Just installing the LivelyKernel files from Github under proper
>>>
>>> apache directory  (as files - is WebDAV needed for this?) gives us
>>>
>>> LivelyKernel functionality, correct? [subquestion that I can answer by
>>>
>>> experimenting - what is the LivelyKernel functionality?]
>>>
>>>
>>> Really good question ;-)
>>>
>>> As of now:
>>> - bootstrap process
>>> - class system
>>> - extensions to JS objects
>>> - "Network" abstraction
>>> - module system
>>> - data bindings
>>> - serialization
>>> - test framework
>>> - Lively morphic v2
>>>
>>> Currently also an OMeta integration and based on that a JavaScript parser
>>> and
>>> interpreter are included.
>>>
>>> We will working on shrinking that however. This is one of the main reasons
>>> for
>>> creating that "fork". See this wiki entry for our motivation.
>> _______________________________________________
>> lively-kernel mailing list
>> lively-kernel at hpi.uni-potsdam.de
>> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel