On Wed, Aug 14, 2013 at 3:40 PM, Peter Drahoš <[email protected]> wrote:
> - Author/Maintainer entries and other useful metadata
>
It seems a small thing, but this is very important. When I package someone
else's code, I don't want to accidentally claim to be the author! I am
just looking after a rockspec, a humble but very useful role.
> - Provided functionality as in LuaDist so modules can replace other
> modules transparently, e.g. luajit provides lua and bitop
>
'provides' is a good concept. To me this is related to alternative
dependencies, since one can merely require something that provides a given
feature.
> - Optional dependencies, as mentioned many times before
>
That's a useful thing (related to build-time dependencies). For instance,
strictly speaking Lake only needs LuaFileSystem, but it acquires extra
super powers if luaposix or winapi are available.
> - Marking external dependencies as optional, LuaDist or any other package
> manager can install them automatically
>
So the maintainer can go to the trouble of specifying the Debian, Fedora or
whatever packages that would satisfy the external need. Extra work, but
users will appreciate this. Currently LR cannot make fine distinctions
about the platform, e.g. Linux can be .deb, .rpm, etc.
- Specification and running of tests
>
There are so many testing frameworks! These can be 'test-time'
dependencies.
> - Documentation install destinations so it can be accessible through
> require (or by other means)
>
Again, so many conventions.
> - Rockspec module metadata install destination and possible accessibility
> by require (or by other means)
>
We've talked about providing an easier way for scripts to query LR for
package information. I think it can be done with a package which can itself
be installed with LuaRocks.
> - Storing component information metadata (eg. installed data files,
> documentation files, module files, executable files …)
>
I'm reading this also as meaning associated data like stylesheets and so
forth. Currently LDoc solves this by making its templates and stylesheets
Lua modules, which is a fine solution if you design for it. It doesn't
work that well for binary assets like images. Assets can be copied into the
rocks tree, but there's no straightforward way to get at them. Ideally we
want a way that doesn't need specific LR hacks in the code itself!
steve d.
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
