I need advice on how to deal with this. Luckily, I am the author of
both lua51 and (upcoming) luarocks packages.
'lua51-dev' package has the developer tools (headers) for compiling
code against Lua 5.1 (liblua).
Normally, packages would only need this for their building, but
luarocks (similar to Ruby Gems but for Lua addon packages) might need
it anytime. Since the user can say "luarocks install" and rocks might
need Lua headers to be around.
So should I simply raise (remove) "BuildDepends only" from the lua51-
dev package, or is there some better approach?
If I do this, will lua51-dev still be allowed into the stable tree?
"headers and the final links from libfoo.dylib into a package which
is classified as BuildDependsOnly: True, and plan to have no other
package depend on this one"
"A maintainer who has reasons to deviate from this policy and not
split the package should explain the reasons in the DescPackaging
field."
- asko
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
