> -----Original Message----- > From: Tom N Harris [mailto:[email protected]] > Sent: dinsdag 28 januari 2014 1:54 > To: [email protected] > Subject: Re: [Luarocks-developers] variables for rockspec > > On Sunday, January 26, 2014 10:08:36 PM Thijs Schreijer wrote: > > Yes, for published rocks. No, for SCM rockspecs. > > > > While testing stuff on a different platform it would allow me to > > fetch/build/install a development branch with a single command. I > > don't want to burden Hisham with a new rockspec for each development > branch. > > > > If this is for testing only and won't be published, then you won't be > bothering Hisham in the first place. Just create your own rockspecs for > private use. Then copy the rockspecs to the target machine, or host your own > rocks server if you want to get fancy. > > As I said, the sticking point is that a rock with the same name and version > would install different things depending on the install flags.
Well, for an SCM rock, that is no problem, as it generally uses the head of the master branch, so it's a moving target anyway. Its sole purpose is to install the latest code, and hence unpredictable version. But, having said that, enabling such a thing would also enable it for common, properly versioned, rocks. And that might be something you don't want. Then again; a rock includes the source and hence the results are fixed... @Hisham; what do you think? Thijs ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
