[Sputnik-list] petrodoc

[pierre pracht]

Le 24 févr. 08 à 12:07, Yuri Takhteyev a écrit :

> I've been playing with the idea of using a single source to generating
> documentation, rockspecs, etc.  Here is the latest version of this,
> which I am calling "Petrodoc":
>
>    http://sputnik-wiki.googlecode.com/svn/trunk/rocks/petrodoc/src/petrodoc.lua
>
> yuri at chai:.../trunk$ rm -rf rocks/colors/tmp/*

The script didn't create the tmp directory.
And the tmp directory isn't part of the repository.

> Colors has just been updated using this method, so you can see the
> html output at http://sputnik.freewisdom.org/colors/.  The rock seems
> to be working.

I'm not sure but :
build = {
    type = "none",
    install = {
       lua = { "src/colors.lua" }
    }
}
This command make a copy of src/color.lua to lua/colors.lua ?

> What do you all think?  I am thinking of switching to this method from
> what is described in http://sputnik.freewisdom.org/en/Source

The generation of documentation and packaging is very nice.
But can't you let the repository directly usable as a rock ?
My setup is :
   - checkout the repository
   - make link in the rock repository (sputnik/cvs-2 -> ../../sputnik- 
orig/rocks/sputnik )
      (need to manually copy : rockspec to sputnik-cvs-2.rockspec)
   - run : luarocks-admin make_manifest

I know that your point of view, is to package yours working files.
But mine is : keep up-to-date copy by just making a checkout.

It would be nice to known other people deal with svn/luarocks.
Any advice ?

- pierre