jyapayne/nimble
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added reasoning for convention for hybrid packages in readme.

Browse source
This commit is contained in:
Dominik Picheta 2015-12-28 16:36:01 +00:00
commit 01bca203a8
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
readme.markdown
View file

@ -443,8 +443,12 @@ of your package.
### Hybrids ### Hybrids
One thing to note about library and binary package hybrids is that your binary One thing to note about library and binary package hybrids is that your binary
will most likely share the name of the package. This will mean that you will may share the name of the package. This will mean that you will
not be able to put your .nim files in a ``pkgname`` directory. The current not be able to put your .nim files in a ``pkgname`` directory. The reason you
will not be able to do this is because binaries on some operating systems
do not have an extension so they will clash with a directory of the same name.
The current
convention to get around this problem is to append ``pkg`` to the name as is convention to get around this problem is to append ``pkg`` to the name as is
done for nimble. done for nimble.