avoid conflicts with other taxonomy-based tools and keep script names consistent (also create taxonomy-directory during installation if not already existing) #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
updateTaxonomy.sh
andupdateAccessions.sh
would be most useful in the PATH. However their more generic name can be a problem if other taxonomy-based tools are installed and use the same naming scheme.To fix that, the KRONA naming scheme of the perl-scripts (with "kt" prefixes) is applied to these scripts via softlinking during installation:
updateTaxonomy.sh
-->ktupdateTaxonomy
updateAccessions.sh
-->ktupdateAccessions
Both scripts are softlinked to the [prefix]/bin folder.
All instances mentioning the use of
updateTaxonomy.sh
orupdateAccessions.sh
inKronaTools.pm
andinstall.pl
have been corrected accordingly.