How to cope with implicit dependencies?

[sschneider-ihre-pvs]

Lets take Lunarvim as an example. Lunarvim installscript will look for Neovim like command -v nvim if nvim is installed with tea it will not find it since it is not in the PATH. also, if you tick the optional installs it would need nodejs and npm, and python and rust along the way.

How do I make this work with tea?

[jhheider]

With an install script, you could do one of the following:

tea +neovim.io +nodejs.org +npmjs.com +python.org +rust-lang.org _install_script_name_

But, more likely what you want is:

for x in nvim node npm python rust; do
  ln -s $(which tea) /usr/local/bin/$x;
done
_install_script_name_

[sschneider-ihre-pvs]

That seems really cumbersome -.- and also you have to iteratively figure out the dependencies manually

[sschneider-ihre-pvs]

With an install script, you could do one of the following:

tea +neovim.io +nodejs.org +npmjs.com +python.org +rust-lang.org _install_script_name_

But, more likely what you want is:

for x in nvim node npm python rust; do
  ln -s $(which tea) /usr/local/bin/$x;
done
_install_script_name_

Would it make sense to give tea a command for linking/shimming that itself? like something tea +nodejs.org --link or so?

[sschneider-ihre-pvs]

With an install script, you could do one of the following:

tea +neovim.io +nodejs.org +npmjs.com +python.org +rust-lang.org _install_script_name_

But, more likely what you want is:

for x in nvim node npm python rust; do
  ln -s $(which tea) /usr/local/bin/$x;
done
_install_script_name_

This doesn't seem to work good with parameters, if for example npm --yes or nvim -u is called

[mxcl]

Yes it makes sense and we have plans to add functionality to make this less cumbersome. Being cumbersome is not our thing.

We’ve only been out 4 months, but we’re trying to get to where you want as soon as possible!

This doesn't seem to work good with parameters, if for example npm --yes or nvim -u is called

We use symlinking for global tools internally at tea for all sorts of things, so it certainly works-for-us. If you can't get it working then please open a ticket and we'll help out or fix things.

[sschneider-ihre-pvs]

scoop on windows does the symlink thing also I think, having a current folder symlink to the current used version and having the executable pointing to that folder so there is no need to update that one every time :D

[mxcl]

What's the context here?

If lunar vim is packaged with tea then all the dependencies are added to the env automatically so lunar vim will find them.

Are you trying to use lunar vim without packaging it for tea as a user or as someone trying to make an install script for lunar vim use tea if it is available?

[sschneider-ihre-pvs]

the former, I guess there is no package for that right now. I was more pointing at the problem with having extendable software with unknown dependencies due to plugins that require a general availability of tools and how to generally cope with those situations.
There is also as it seems a context problem with tools like npm where the node_modules in the current folder is not recognized if used with tea for example.

[sschneider-ihre-pvs]

I really like the magic of tea, I only have difficulties with managing dependencies of stuff not packaged with tea that also should use stuff that tea has to offer.