Hi David,
which sites are blocked?
Can you access tools that take it's binaries from
https://github.com/galaxyproject/cargo-port?
If so Eric has ported all URLs over to cargo-port sometime ago. So we
just need to update the packages for you.
This only holds true for IUC packages and we
Hi David,
one thing that you might be missing is that the wrapper for the
infosec-approved version might not exist yet (you would have to adapt the
older shed-wrapped version if there were any relevant changes). But this
largely depends on what software you want to use.
Besides that your flow
David,
You can have multiple versions of tool 'installed' manually (i.e. without
shed).
That said, there is an option of working with the IUC to make the wanted
packages to be up-to-date and secure. i am pretty sure any PRs this
direction will get merged.
M.
On Wed, Apr 13, 2016 at 11:39 AM
Hi Bjoern,
Yes, we can reach stuff in the cargo-port. Unfortunately doing that isn’t a
solution as the package that concerns our infosec is the same older version
there in cargo-port as it has been trying to pull from SourceForge. Galaxy
might be able to get it then, but I’m not permitted to
Nicola,
Thanks! I completely missed that. That’s very useful to know.
Martin – yes a PR is on the to-do list, but unfortunately it’s a low-ish
priority as the wish is to be using system / module deps. Have an impending
vacation, so am having to get through a lot of stuff right now. Hopefully
Hi Martin,
Thanks for the input - yes there is going to be maintenance headache either
way, private tool-shed or not. If we don't go with our own tool-shed though, am
I right in thinking we lose versioning for tools? I.E. installing manually into
'tools' and tool_conf.xml I can't use tags
Hi David,
in the server I am administering I don't use the Tool Shed dependency
resolver and is not much work if you are used to environment modules.
For more information, see:
https://docs.galaxyproject.org/en/master/admin/dependency_resolvers.html
Cheers,
Nicola
On 13/04/16 16:42, Martin
