# HG changeset patch
# User bgruening
# Date 1620370082 0
# Node ID 850347f034dee69a3ee70ed6d89917fdeffcefe2
# Parent  be717b65851ff971710c94b8a2e19893eef0e717
"planemo upload for repository https://github.com/bgruening/galaxytools/tree/master/tools/nanopolish commit 4883f9a9a2779e2b4792314bd6128c7c109c00e1"

diff -r be717b65851f -r 850347f034de test-data/all_fasta.loc
--- a/test-data/all_fasta.loc	Fri May 29 13:30:45 2020 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-draft	draft	draft	${__HERE__}/draft.fa
\ No newline at end of file
diff -r be717b65851f -r 850347f034de test-data/all_fasta.loc.sample
--- a/test-data/all_fasta.loc.sample	Fri May 29 13:30:45 2020 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-draft	draft	draft	${__HERE__}/draft.fa
\ No newline at end of file
diff -r be717b65851f -r 850347f034de tool-data/all_fasta.loc.sample
--- a/tool-data/all_fasta.loc.sample	Fri May 29 13:30:45 2020 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,19 +0,0 @@
-#This file lists the locations and dbkeys of all the fasta files
-#under the "genome" directory (a directory that contains a directory
-#for each build). The script extract_fasta.py will generate the file
-#all_fasta.loc. This file has the format (white space characters are
-#TAB characters):
-#
-#<unique_build_id>	<dbkey>	<display_name>	<file_path>
-#
-#So, all_fasta.loc could look something like this:
-#
-#apiMel3	apiMel3	Honeybee (Apis mellifera): apiMel3	/path/to/genome/apiMel3/apiMel3.fa
-#hg19canon	hg19	Human (Homo sapiens): hg19 Canonical	/path/to/genome/hg19/hg19canon.fa
-#hg19full	hg19	Human (Homo sapiens): hg19 Full	/path/to/genome/hg19/hg19full.fa
-#
-#Your all_fasta.loc file should contain an entry for each individual
-#fasta file. So there will be multiple fasta files for each build,
-#such as with hg19 above.
-#
-