On Sat, Mar 10, 2012 at 3:25 PM, Alexander Gladysh <[email protected]> wrote: > On Sat, Mar 10, 2012 at 11:21, Hisham <[email protected]> wrote: > >> I'm wondering if the remote rocks server URL should be versioned as >> well -- I'm hoping not, as I don't want to keep two repositories. >> Hopefully with proper dependencies specified in rockspecs we'll be >> able to get away with a single repository (some rockspecs will need to >> be revised to explicitly mention (in)compatibility with Lua 5.2). > > How would you handle binary rocks? > > ABI is different... A source rock may handle this by #ifdef-ing stuff, > but what to do with compiled one?
Well noted. In terms of usage, it's more of a configuration thing. In terms of tool support, there could be metadata in the rock to indicate which ABI it is compiled against, to prevent from installing incorrect rocks. On the luarocks.org end, it's a matter of managing repositories. My initial thought would be to remove all binary rocks from the main repository -- there are only some win32 packages there -- and create a separate "win32 binaries" URL (we don't actively maintain the repository win32 binary rocks anymore, though, and that repo could be instead part of "LfW extras" or something like that). -- Hisham ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
