[Sputnik-list] blueprint

[pierre pracht]

Le 15 févr. 08 à 04:03, Yuri Takhteyev a écrit :
>>> You must explain a bit your work flow.
>
> At this point I keep all of my code in "rocks" separated by which
> "rock" it will be released with.

So trunck/rocks contain repertory ready to be packaged as rocks
It's neither :
   - rocks ready to install
   - modules ready to be imported by lua

> I often have a few versions running at the same
> time.)  If I want to make sure that a particular rock is up to date
> relative to SVN then I go through the steps that I just described on
> the wiki:
>
> http://sputnik.freewisdom.org/en/Installing_from_SVN

To see If have understood :
   - You edit in trunk/rocks
   - To test you push (copy) edited version in share/lua/5.1/
   - To keep a trace of change you commit to svn
   - At a point you run a script
       to bundle a repertory of trunk/rocks as a rocks

>>>>   "/opt/sputnik2/sputnik-svn/rocks"
>
> "file:///opt/sputnik2/sputnik-svn/rocks"

Can't work as trunck/rocks isn't a rocks repository ! wrong ?

>> Luarocks would handle the (base) path ? See above.
>
> LuaRocks just adds each rock to your search path.  So, when you say
> require("sputnik.actions.blueprint_css"), Lua will go through every
> rock looking for
> <rock_name>/<version>/lua/sputnik/actions/blueprint_css.lua and will
> use the first match it will find.  (It's a bit of a simplification
> because LuaRocks may filter the search by <version>.)

I have take this functionality of Luarocks for an other workflow :
  - make a regular install of lua , rocks , sputnik ...
  - checkout svn trunk/rocks to sputnik-rocks
  - make symbolic link : rocks/sputnik/cvs-1 -> ../../sputnik-rocks/ 
sputnik
    Rq: need to change
      sputnik-rocks/sputnik/rockspec in
      sputnik-rocks/sputnik/sputnik-cvs-1.rockspec
  - run bin/luarocks-admin make_manifest

By this way you can have many install of lua/rocks with many working  
copy of svn. You simply build symbolic links between each.

I don't know what are recommendation regarding SCM / LuaRocks, but :

If you change in the repository rockspec in $ROCK-cvs-1.rockspec you  
have just a line to change in your script.

An other way(not tested) is to simply checkout svn trunck/rocks/$ROCK  
to local rocks/$ROCK/cvs-1
So if you change svn layout with cvs-1 repertories, it would make it  
more explicit.
I the same time, it would ease symbolic link creation.

I don't know if LuaRocks have some policy / docs / helper for this,  
but It would have been very helpful for me. I have spend 2 day just to  
get a correct setup.

Need to take a break :(

>> I would, but I need my new setup to work !
>> With "Sputnik on the Rocks" I wasn't able to use CGI
>
> Let me look into this.  It's possible that wsapi rock changed.

I took your last install script, it work fine.
I get xavante so no extra / config
your xavante work with CGI so no server restart
Rq: first instal was done with xavante/wsapi (painful !)

- pierre