Failed to find dependencies: dot:from<bin>

[AntonOks]

Cloning this GIT REPO and than trying to install in via zef install . results in:

~/temp/Git/Github/rakudo_star/src/rakudo-star-modules/Perl6-TypeGraph$ zef install .
===> Searching for missing dependencies: dot:from<bin>
Use of Nil in string context
  in block  at /home/anton/temp/Git/Github/rakudo_star/share/perl6/site/sources/020B1DCFD2D1C1C1948036C328066D9F71CCE234 (Zef::Repository) line 143
Use of Nil in string context
  in block  at /home/anton/temp/Git/Github/rakudo_star/share/perl6/site/sources/020B1DCFD2D1C1C1948036C328066D9F71CCE234 (Zef::Repository) line 143
Use of Nil in string context
  in block  at /home/anton/temp/Git/Github/rakudo_star/share/perl6/site/sources/020B1DCFD2D1C1C1948036C328066D9F71CCE234 (Zef::Repository) line 143
===> Failed to find dependencies: dot:from<bin>
Failed to resolve some missing dependencies (use e.g. --exclude="dot" to skip)

[JJ]

Generally, zef will not be able to find this kind of dependencies. You will need to install them in advance, I'm afraid. If you feel that the documentation does not cover this properly, just let me know.

[AntonOks]

Generally, zef will not be able to find this kind of dependencies. You will need to install them in advance, I'm afraid. If you feel that the documentation does not cover this properly, just let me know.

1. Sorry, now I'm lost. Whats the META6.json file, especially the "depends" section there, good for than?
2. It's stated everywhere, that a "RAKU module" should be installable by ZEF from within it's "source", right? ZEF auto-resolves the defined dependencies usually.This isn't working here so saying "zef will not be able to find this kind of dependencies...." seems to be a very "only-this-module-has-this-problem" specific issue, right?

[JJ]

Generally, zef will not be able to find this kind of dependencies. You will need to install them in advance, I'm afraid. If you feel that the documentation does not cover this properly, just let me know.

1. Sorry, now I'm lost. Whats the META6.json file, especially the "depends" section there, good for than?

Well, I'm lost. Is that an issue in this specific module?

2. It's stated everywhere, that a "RAKU module" should be installable by ZEF from within it's "source", right? ZEF auto-resolves the defined dependencies usually.This isn't working here so saying "_**zef will not be able to find this kind of dependencies....**_" seems to be a very "only-this-module-has-this-problem" specific issue, right?

OK, you threw a curveball back into my field, that's a good one. I'll try to catch it or dodge it 👍 .

If you look at the documentation, it is also used in Inline::Python and probably elsewhere; it's spec as far as I can tell, and also AFAICT intended for future hooking into binary, OS-specific, installation hooks that, unfortunately, do not exist as of yet. So, in this case, the error it throws is a polite way of saying read the installation section of the manual. You might want to look at this discussion, specifically where @ugexe says:

no, its not meant to allow zef to install native dependencies (although doing so is fairly straight forward). It fixes the native dependency problem for the common case by simply giving a missing dependency error that the developer can act on, all without downloading or running any code.

Tell me anyway if there's something specific I can do to help you with this specific module, documentation-wise or other.

[AntonOks]

Generally, zef will not be able to find this kind of dependencies. You will need to install them in advance, I'm afraid. If you feel that the documentation does not cover this properly, just let me know.

1. Sorry, now I'm lost. Whats the META6.json file, especially the "depends" section there, good for than?

Well, I'm lost. Is that an issue in this specific module?

2. It's stated everywhere, that a "RAKU module" should be installable by ZEF from within it's "source", right? ZEF auto-resolves the defined dependencies usually.This isn't working here so saying "_**zef will not be able to find this kind of dependencies....**_" seems to be a very "only-this-module-has-this-problem" specific issue, right?

OK, you threw a curveball back into my field, that's a good one. I'll try to catch it or dodge it 👍 .

If you look at the documentation, it is also used in Inline::Python and probably elsewhere; it's spec as far as I can tell, and also AFAICT intended for future hooking into binary, OS-specific, installation hooks that, unfortunately, do not exist as of yet. So, in this case, the error it throws is a polite way of saying read the installation section of the manual. You might want to look at this discussion, specifically where @ugexe says:

no, its not meant to allow zef to install native dependencies (although doing so is fairly straight forward). It fixes the native dependency problem for the common case by simply giving a missing dependency error that the developer can act on, all without downloading or running any code.

Tell me anyway if there's something specific I can do to help you with this specific module, documentation-wise or other.

My original issue was... this module is part of the "Star" release, but ZEF cannot install it.

I've now learned, that a(nother) pre-requirement for this module seems to be graphviz, right?

So, as this module cannot be installed by ZEF "out of the box", I will remove it from the "Star" modules list. Would that be ok with you?

THANKS for your feedback / help!

[JJ]

Generally, zef will not be able to find this kind of dependencies. You will need to install them in advance, I'm afraid. If you feel that the documentation does not cover this properly, just let me know.

1. Sorry, now I'm lost. Whats the META6.json file, especially the "depends" section there, good for than?

Well, I'm lost. Is that an issue in this specific module?

2. It's stated everywhere, that a "RAKU module" should be installable by ZEF from within it's "source", right? ZEF auto-resolves the defined dependencies usually.This isn't working here so saying "_**zef will not be able to find this kind of dependencies....**_" seems to be a very "only-this-module-has-this-problem" specific issue, right?

OK, you threw a curveball back into my field, that's a good one. I'll try to catch it or dodge it +1 .
If you look at the documentation, it is also used in Inline::Python and probably elsewhere; it's spec as far as I can tell, and also AFAICT intended for future hooking into binary, OS-specific, installation hooks that, unfortunately, do not exist as of yet. So, in this case, the error it throws is a polite way of saying read the installation section of the manual. You might want to look at this discussion, specifically where @ugexe says:

no, its not meant to allow zef to install native dependencies (although doing so is fairly straight forward). It fixes the native dependency problem for the common case by simply giving a missing dependency error that the developer can act on, all without downloading or running any code.

Tell me anyway if there's something specific I can do to help you with this specific module, documentation-wise or other.

My original issue was... this module is part of the "Star" release, but ZEF cannot install it.

Right... I'm not totally sure why that was the case in the first place; maybe because it was used to generate the documentation. I've lost track of what's the state of that as of now, but whatever the case, I don't think it's a good idea to put this into the Rakudo Star distribution, if not for anything else, precisely for this reason, because it needs additional external programs that might or might not exist in specific operating systems.

I've now learned, that a(nother) pre-requirement for this module seems to be graphviz, right?

So, as this module cannot be installed by ZEF "out of the box", I will remove it from the "Star" modules list. Would that be ok with you?

As said above, it's totally reasonable. Will that close this issue?