On Thu, Oct 14, 2010 at 11:25 AM, Alexander Gladysh <[email protected]> wrote: > On Thu, Oct 14, 2010 at 18:16, Hisham <[email protected]> wrote: >> On Wed, Oct 13, 2010 at 9:11 PM, Alexander Gladysh <[email protected]> >> wrote: >>> Hi, list! > >>> I store my private LR repo manifest in git. > >>> Update-manifest often changes it needlessly: > >>> <td class="version"> >>> -scm-1: <a href="json2lua-scm-1.rockspec">rockspec</a>, <a >>> href="json2lua-scm-1.all.rock">all</a><br/></td></tr> >>> +scm-1: <a href="json2lua-scm-1.all.rock">all</a>, <a >>> href="json2lua-scm-1.rockspec">rockspec</a><br/></td></tr> >>> <tr><td colspan="2" class="spacer"></td></tr> > >>> Please sort the output. > >> Is that on 2.0.3? I did add some sorting to the code recently, but I >> think it's only on git for now. > > Right. > >> Anyway, I thought the recommended policy was not to store >> automatically generated files (e.g. configure scripts) in SCM >> repositories. > > This is a special technical repo dedicated to be able to *quickly* > restore the one of previous system states. It intentionally contains > all pre-built files. When you realize that you deployed something bad > you always want to revert ASAP.
I believe the current state of git is that index.html is properly sorted but manifest isn't -- it is just a simple serialization of the table. I can't look closely at it right now but maybe it's just a matter of changing pairs() to util.sortedpairs() in luarocks.persist. Please give it a try and let me know how it goes. Thanks, -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
