Isn’t it better if we would use a submodule for elib in Yellowgrass to make it easier to track which version of elib is used for yellowgrass?

Submitted by chris melman on 3 January 2013 at 15:00

Sure. How do we set that up?

I guess we will (eventually) move to a different theme than the default one in elib. Submodules still usable?

I have pushed it to github so when you pull and use

 git submodule update --init --recursive 

it will give you elib as submodule.

lookout first push changes of elib to github en remove the folder.

it should be no problem to fix themes,
the best way is probably import/rename css files and put them in the general stylesheet folder
other soltion would be to branch elib, however I guess that will deliver more work later on to keep it up to date.