[Sputnik-list] petrodoc
Yuri Takhteyev
yuri at sims.berkeley.edu
Fri Feb 29 08:34:23 GMT+2 2008
> The script didn't create the tmp directory.
> And the tmp directory isn't part of the repository.
Whoops. Yes, the script should create it. I'll fix it.
> 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 ?
No, I changed "lua" to "src" in svn for colors. I am thinking of
doing it for everything else too, since "src" seems more standard.
But it wouldn't be hard to convince me not to.
> 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.
I don't have anything against running everything fresh out of SVN, I
just haven't gotten around to figuring out a good way to do that and
packaging rocks has been a higher priority. So, you tell me: what
should we do? I didn't quite understand your solution. Note that
alternatively we could write a script that would generate make
symlinks from some directory (e.g., ~/sputnik/share/lua/5.1) to all
the files in the rocks.
> It would be nice to known other people deal with svn/luarocks.
> Any advice ?
Perhaps this is a good question to ask on luarocks-developers?
- yuri
--
http://sputnik.freewisdom.org/
More information about the Sputnik-list
mailing list