I have created a tool that depends on biopython. I don't like the idea
of having several copies of biopython around and also for best
practice making workflows using my tool reproducible, I chose to make
my package repository dependent of package_biopython_1_62.
I'm installing my package using the virtualenv option. As you can see
below I marked biopython as prior_installation_required="True".
However, I can see that virtualenv is installing a copy of biopython
in 'venv' under my tool install(see below). This doesn't sound right.
I was expecting that by making my repository dependent of biopython's
one that source would be used in my tool.
My plan is to create any non-existing "Tool dependency definition"
repository for every package my tool requires. This way you can always
count the same version of any of these packages is being used. I
thought that was the point, right?
<package name="biopython" version="1.62">
<package name="ngs-tools" version="0.1.6">
Contents of site-packages in my tool install dir:
$ ls -1
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: