On 9 October 2011 09:53, Alexander Gladysh <[email protected]> wrote: > > Reuben, since you make announcements with script, in the next release > please CC LR list and explicitly add a link to the rockspec.
My release script sends the rockspec to the list! > (Also, please do store generated rockspecs in the main luaposix Git — > otherwise you make life harder for end-users like me.) I prefer not to store generated files in Git. I would like to ship the rockspec in the distribution archive, but the trouble is that this seems to create a catch-22, as the rockspec depends on the MD5 sum of the archive, which in turn depends on the rockspec. There's a similar catch-22 in the Makefile: the rockspec depends on the dist target, so making the dist target depend on the rockspec would create a loop. I'm happy to hear suggestions, but of course the rockspec for a release is always available from the LR dev list, and, shortly afterwards, from luarocks.org. Also, it's possible to make it from a git checkout for any given release. -- http://rrt.sc3d.org ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
