On Tue, Dec 4, 2012 at 5:45 PM, Gerhard Lipp <gel...@gmail.com> wrote: > Hello Leaf! > I'd love to have some more "open" approach for managing the rockspecs. Maybe > homebrew might be a good place to look > (https://github.com/mxcl/homebrew/wiki/Formula-Cookbook). The repository for > the formulas (->rockspecs) is basically a github project. If you want to add > or improve something, just fork and make a pull request. > I was pretty impressed to see how neat homebrew integrates with the github > workflow and I was thinking this might be just great for luarocks as well.
A LR repository is just a directory with a manifest file. It can be hosted anywhere that can provide those files over http/https, or even from a local filesystem directory. I _think_ (but I'm not sure) that a github repo can work as a rocks server even today (if they don't do funny things with URLs). > In particular I like that you can test the new repository / changes you made > on your computer with no extra infrastructure. Well, LR doesn't really need a lot of infastructure now: you can already just do `luarocks --from=/any/local/dir build bla` or `luarocks build ./bla-1.0-1.rockspec`. > @Hisham: This appraoch may safe you a lot of time fixing rockspecs etc, dont > you think? But yes, definitely. I'm really excited about Leaf's MoonRocks project -- we've discussed about it offlist already. (But still I need to congratulate him publicly: great work!!) I'm eager to hear what the community thinks about it, especially with regard to things such as: Leaf Corcoran wrote: > When you upload a new module, it goes into your own personal manifest at > first. You need to add it to the root manifest manually for the time being. > (I'm still trying to think of the best way to handle this. Should modules > require approval before going into root manifest, or can anyone put modules > in there?) There are many possibilities around this. One idea would be to have an admin team to go through initial submissions and after the first approval, rock owners could then add new versions directly to the root manifest (I take it from my usual experience as the current care taker of the default repo: I usually check more carefully new submissions, to see if the rockspec is written correctly, good descriptions, provide feedback to the author etc, and then later submissions of new versions are a much quicker process in which I just send the rockspec through a script to check if the URL works, pack the .src.rock, etc.). So, yes, I'm as eager as Leaf is to hear feedback on this. I can see MoonRocks evolving into the default repo (which I totally agree that's currently overly conservative in its management), once we figure out how we want to use it as a community. -- Hisham http://hisham.hm/ ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
