On 23 May 2014 06:59, Marc Balmer <m...@msys.ch> wrote:
> Hmm, indeed. So maybe something is not OK with how I put stuff on github,
> maybe someone can elighten me how I best prepare my software to make it
> easy to "rock" it.
>
> Should these rockspec files be kept outside the sources themselves or
> should I include them in the repository?
>
Standard behaviour seems to be keeping an 'scm' rockspec in the root of
your repository.
Personally; when I make as I make a tag/release; I 'git mv' and edit
version in the rockspec.
One of my better-kept examples is probably luatz (
https://github.com/daurnimator/luatz )
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
