Riley, I think this is a good suggestion -- we need an easier way to manage SDAP dependencies and transitive dependencies, especially given the license issues we've come across multiple times now. This would also make building the software locally a lot easier. I'm a big fan of poetry in particular and think it would suit SDAP well.
I'm also supportive of combining the analysis and data-access packages into a single package - the current organization makes development more tedious without much benefit -- especially because they are packaged together in the Docker container anyways. Stepheny On 2024/02/28 22:07:34 Riley Kuttruff wrote: > We currently use conda/mamba to install dependencies for the granule ingester > and Nexus components in both local dev environments and for building Docker > images. This seems to have unwanted consequences as Docker appears to be > forcing inclusion of some GPL-licensed tools and libraries that we don't seem > to use but likely block releases under ASF policy. This issue was brought up > in our IPMC graduation discussion as needing to be solved. > > I'd like to propose replacing conda with another package manager like poetry > or simply using pip. We could also take this opportunity to combine the two > top-level Nexus modules so that they're not individual-yet-interdependent > modules with their own dependencies, but rather two submodules of a single > project with a single, shared list of dependencies. >
