add bin-script known issue to readme

[Tieske]

No description provided.

[coveralls]

Coverage decreased (-4.4%) to 83.254% when pulling b06b99c on Tieske:master into be9319d on hishamhm:master.

[Tieske]

Since coverage decreased by updating the readme (?), I had a look at the test configuration and updated that as well, to include only the actual datafile code and nothing else.

[hishamhm]

Oh, this is a nasty limitation. I'm not even sure I was aware of it. I'd rather try to think a way to fix it rather than just documenting it.

I'll give this some thought. At first glance it doesn't sound like something fully fixable in pure Lua, but we might do some heuristics like using arg[0] and maybe OS-specific environment variables.

[Tieske]

You cannot fix it. Because multiple rocks might write the same script in the bin directory (overwriting each other, which is another problem, but that is what it is because it is in the system path). And because of that, it cannot be fixed.

By the way: the description is a bit elaborate. A shorter version would be to move the commandline script in a module. And add a bootstrap-script in bin that loads and executes the module.

[hishamhm]

@Tieske if we're dealing with a LuaRocks-installed bin script, the luarocks-aware datafile loader should be able to cheat and ask the LuaRocks loader about it.

I'll try hacking something together.

[Tieske]

ping @hishamhm

[hishamhm]

@Tieske I could not reproduce this. When I run cd test; luarocks install test-datafile-scm-1.rocksec and then I run the installed test_script, it works.

BTW, I just pushed release 0.6 with a fix for LR3.

[hishamhm]

I'm closing this for now -- if the problem persists, let's reopen and discuss.

[Tieske]

@hishamhm can you merge the .luacov config file anyway?