Open bioinfornatics opened 5 years ago
This software runs on the .net core runtime so I'm not sure the same standard for native Linux distributions makes a lot of sense. The .net core runtime has specific rules for resolving library dependencies that don't follow the Linux conventions for .so files.
With our current release, each separate executable is free to depend on its own version of any library (or binary such as tabix). This does create file duplication, but also provides freedom to not upgrade dependencies for every subcomponent unnecessarily (reduced test burden).
We could have a separate installation script for each .net main entry pointy that creates the structure as you describe, but the primary Canvas entry point will need to know where each executable lives. Using Linux PATH to find each entry point is one option, but rather than requiring additional configuration via PATH modification, the paths are implicitly defined by the filesystem hierarchy.
Dear,
Currently the way to provides each canvas release imply to have multiple copy of the same library such as Isas.Framework.dll, same executable such as tabix.
This is error prone and do not follow standard packaging system see the FHS
Why is error prone ? using your release archive we can see that for a same library different version are used !
Same for tabix
And so on ...
You should provide a standard compliant archive like this:
To do this you could use this script in the future (once you have the same version see above):
Thanks