alecbcs / lookout Goto Github PK

I want to open an issue to list some potential issues that we discussed today, which I'd love to give a first stab at (and likely I'll be able to make some time next week) - I love GoLang too but don't get the opportunity to work with it super often.

Lookout search

The use case I have in mind is when the user doesn't have a package installed, and isn't privy to what the latest version is. We might support either of the following:

• some kind of search, e.g., added with lookout search that would look for the package in some registry (file) of known software packages, and then return to the user the latest version (or some subset of versions in a small table depending on what they ask for).
• but arguably this same search could be integrated with the lookout add to allow for a more seamless interaction that doesn't require more than one command. For example:

$ lookout add singularity
...<does search, shows latest version, asks user "would you like to add version X from <resource> Y/n>?

I think we would want a user to be able to do lookout add <tool> without needing to know the registry or version in advance. If lookout is setup to basically try to help get to the latest version, then the default should probably be the latest found.

Lookout import

It would be super cool to have some existing lmod / spack / other install, and quickly "import" current versions into lookout. I think what I want to think about more is how these two things can be coupled easily so even a user could write some custom script to, e.g., find packages that need update, update or build a container, or some custom thing.

Feedback on organization and color of lookout

We chat about this in the call -I think we can we better organize the current and latest by either putting them each just on one line, or grouping them together more obviously for the user.

A way to import an entire already existing package base (spack,lmod)

I'm trying to reproduce the example you showed me, I tried for both singularity and the example in the README, both don't work!

$ ./lookout add cuppa 1.1.0 https://github.com/DataDrake/cuppa/archive/v1.1.0.tar.gz
2020/10/02 17:26:40 Unable to find cuppa https://github.com/DataDrake/cuppa/archive/v1.1.0.tar.gz

I think I'm probably forgetting something... I shouldn't need to export a GitHub token for using the API, and if I did need to, there would be a warning right? What am I forgetting?

$ ./lookout add singularity 3.6.3 https://github.com/hpcng/singularity/releases/download/v3.6.3
2020/10/02 17:25:58 Unable to find singularity https://github.com/hpcng/singularity/releases/download/v3.6.3