# HG changeset patch
# User yhoogstrate
# Date 1472201268 14400
# Node ID ac246b8ab8a52c16f7569b8d9cf97f8713f0aef8
# Parent  e38348dbd63f0f27cf457178f842455bc38530fe
planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/star_fusion commit 38b164ccb9b3cdfb58d83cdc1f05063a40123bab-dirty

diff -r e38348dbd63f -r ac246b8ab8a5 tool-data/all_fasta.loc.sample
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tool-data/all_fasta.loc.sample	Fri Aug 26 04:47:48 2016 -0400
@@ -0,0 +1,18 @@
+#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.
+#