The two currently not used procedures `getSpecificDir` and `doPull` from
`download.nim` file are reverted according to dom96's suggestion in the
code review of pull request #692. Now they are marked with used pragma
to disable the warning.
Related to #680
There are two issues fixed:
- With the latest Nim version sometimes the files
`<package_name>_<some_number>.nims`' generated on `nim install`
contain warning for unused imports which causes the test
"can validate package structure (#144)" to fail, because it was
searching for the word "warning" in the output.
- On Windows Subsystem for Linux, when an import starts sometimes with
a lowercase, and sometimes with an uppercase, for example
`import uri` and `import Uri`, this causes Nim to create and compile
both `stdlib_uri.nim.c` and `stdlib_Uri.nim.c` and to fail on the
linking step, because of the same symbols are being redefined.
Also the Travis CI build script is changed to test against currently the
latest working Nim version 212ae2f.
Related to #680
The directory "tests/buildDir/" where the build artifacts from the
"compilation without warnings" unit test execution are being written is
added to the .gitignore file.
Related to #680
Compilation without warnings test case on Unix systems with older Nim
version 0.19.6 had been failing before the fix, because the compiler
expects full file name to be passed after the '-o' switch, but not only
an output directory name.
Related to #680
The NimbleError exception from the version module is being used only on
Windows platforms in the packageinstaller.nim file. Conditional import
of the module is used to fix the warning.
Related to #680
An unit test which checks whether Nimble compiles without warnings is
added. Checking for three warning types cleaned in previous commits is
implemented:
- [UnusedImport] cleaned in e8c7d5c
- [Deprecated] cleaned in 3d6172e
- [XDeclaredButNotUsed] cleaned in 7df2ef3
Other types of warnings easily can be added to the test by extending the
warnings list.
Related to #680
To compile the nimscriptapi.nim file, it is needed to import the os
module, but if so the getParams procedure cannot be executed from
nimscript any more. The problem is resolved by conditionally importing
the module.
Related to #680
This fix clears deprecation warnings related to Nim's HashSet
procedures. There were two types of warnings which have been fixed:
- Warning: Deprecated since v0.20, use 'initHashSet'; initSet is
deprecated [Deprecated]
- Warning: Deprecated since v0.20, use 'toHashSet'; toSet is
deprecated [Deprecated]
Backward compatibility with older Nim versions is also implemented.
Related to #680
* Fix#567: Display package versions in sorted order
* Add docs
* Fix docs to focus on git tags
* Refactor to use version module
* Streamline docs
* Refactor to make things work in nim <= 0.19.6
* Improve code readability
After the ownership of the issue678 test repository was transferred to
the nimble-test account, the links to the repository required for
performing the test had to be updated in order to avoid possible
confusion, despite the fact that GitHub does automatic link redirection
for transferred repositories.
Related to #687
When one package is dependency both of some other package and some other
dependency of the other package it has been downloaded and installed
multiple times.
Resolves#678
Several additional file and folder types are added to .gitignore:
- VSCode directory for for user and workspace settings.
- *.orig files created by Git on merge conflicts.
- Some artifacts related to the test procedure.
since it replaces characters used in many names and languages with
escape sequences.
Slightly refactor the code for determining author name, to make it
easier to add other version control systems in future (right now it's
just git and hg).
Also, add some binary test artifacts to .gitignore so they don't accidentally
get committed in future.
