[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Dependency graph of top 350 rocks in luarocks.org
- From: Adrián Pérez de Castro <aperez@...>
- Date: Fri, 29 Jul 2016 10:46:58 +0200
Quoting Alban Linard (2016-07-29 09:17:22)
> It seems strange that projects depend on testing tools, such as busted, as this dependency is usually used __only__ for development.
>
> I always end up writing two rockspecs: one to install development environment (busted, cluacov, luacheck, …) and a real one for the non-development dependencies, that is uploaded to luarocks.org.
>
> Is there a way to specify in one rockspec the distinction between dev dependencies and others ? Is there a better solution ? Good practices ?
Some days ago I had the same issue and wondered whether there is some way of
having “development dependencies” in a rockspec, but after reading through the
LuaRocks documentation the answer seems to be “no”. For now I have settled on
not adding the testing/development dependencies to my rockspecs, and trust
that the developers (that is: myself) will figure out how to install the
development dependencies :-)
> > Le 28 juil. 2016 à 23:11, Hisham <h@hisham.hm> a écrit :
> >
> > Hi,
> >
> > I saw this on Twitter, and the author gave me the green-light to share
> > it, so I thought some of you would enjoy it:
> >
> > By @syaffers: « Dependency graph for top 350 most dl'ed rocks. Data
> > crawled from #luarocks (sry!) #lua http://bit.ly/29wNtix »
> >
> > Tweet:
> > https://twitter.com/syaffers/status/752078854370439168
> >
> > Direct link to the image:
> > https://s3.amazonaws.com/syaffers-stuff/h350.svg
Nevertheless, the graph is quite cool!
--
☛ Adrián
Attachment:
signature.asc
Description: signature