split LivelyKernel repo about livelykernel HOT 7 CLOSED

I like the idea. Would we still have a possibility in core/ to run tests without any other repo?

from livelykernel.

the tests are part of core, so using lively's test runner yes. but i would like to make the test scripts part of the lk-script repo and move the core/ content of this repo to the top-level.

from livelykernel.

+1

from livelykernel.

we are slowly getting there... I will make a pull request for a proposal of how the repositories can be laid out.

from livelykernel.

OK, I gave that some thought and I think I should have time in the next couple of days, so here is what I want to do

Step 1: make our current repo the real core repo, move the contents of the core/ folder to the toplevel and split a lk-scripts repository

Step 2: the lk scripts either go into a subfolder .scripts/ as as a git submodule || would become a separate npm module.

The downside with the submodule is that a) submodules suck and b) you don't wanna have all the scripts every time you want just the core code. Having both a npm module for the scripts and LivelyKernel core would allow us install the scripts as a dependency when using npm and get the vanilla core repo when just cloned with github.

(Another alternative would be to have the scripts repo act as the npm LivelyKernel module and add LivelyKernel core as a npm dependency or git submodule to that)

Any thoughts?

from livelykernel.

Two npm modules with deps look a lot cleaner to me.

git submodules and checkout with filters sounds a lot like the stuff we didn't like about svn ("only check out file1, .., fileN in order to obtain the core").

from livelykernel.

OK, it now works like that:

• scripts are installed with npm install -g livelykernel-scripts. This will install the lk tool into /usr/local/bin which should be in PATH by default.
• lk workspace --init will then automatically get a copy from the LivelyKernel core git repo and from the webwerkstatt core and will put those into scripts/workspace/lk and scripts/workspace/ww. This is the default place for lk/ww working copies meaning that those are used whenever a lk script needs the lk/ww dir and no specfic --lk-dir/--ww-dir parameter is given. Instad of installing those with workspace init you can also symlink those (the travis build script does that for example).

from livelykernel.