Closed rvosa closed 4 months ago
This shouldn't be a problem... @bwprice has suggested renaming the tool to skim2mito? How do we feel about another name change?
+1 million on a name change to skim2mito - much easier to say :)
I don't care what it's called as long as it's reasonably unique. In the end, the conda environment is just going to be a folder on a computer and that folder can't be called 'snakemake' because there could easily be one by that name already there. 'skim2mito' is fine for that.
Name of tool and top level conda environment updated to skim2mito
[heart] Ben Price reacted to your message:
From: Ollie White @.> Sent: Tuesday, June 25, 2024 1:26:54 PM To: o-william-white/skim2mito @.> Cc: Ben Price @.>; Mention @.> Subject: Re: [o-william-white/skim2mito] renaming the top-level conda environment (Issue #28)
Name of tool and top level conda environment updated to skim2mito
— Reply to this email directly, view it on GitHubhttps://github.com/o-william-white/skim2mito/issues/28#issuecomment-2188967422, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACG2URLLGA3TUJRRJ6FW37DZJFVZ5AVCNFSM6AAAAABHNC45RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYHE3DONBSGI. You are receiving this because you were mentioned.Message ID: @.***>
The top-level conda env in workflow/envs/conda_env.yaml is now referred to as 'snakemake', although it is a bit richer than just snakemake. To avoid name clashes in host systems, perhaps this can be renamed to skim2mt