[bug] module cannot be instlled with ZEF

[AntonOks]

On UBUNTU:

$ zef install . --force-test
===> Searching for missing dependencies: Doc::TypeGraph
===> Searching for missing dependencies: dot:from<bin>
Use of Nil in string context
  in block  at /home/user/temp/Git/GitHub/rakudo_star/share/perl6/site/sources/020B1DCFD2D1C1C1948036C328066D9F71CCE234 (Zef::Repository) line 143
Use of Nil in string context
  in block  at /home/user/temp/Git/GitHub/rakudo_star/share/perl6/site/sources/020B1DCFD2D1C1C1948036C328066D9F71CCE234 (Zef::Repository) line 143
Use of Nil in string context
  in block  at /home/user/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)

On Windows11:

PS C:\Temp\Git\doc> zef install . --force-test
===> Searching for missing dependencies: Doc::TypeGraph
===> Searching for missing dependencies: dot:from<bin>
Use of Nil in string context
  in sub warn at 'SETTING::'src/core.c/control.pm6 line 269
Use of Nil in string context
  in sub warn at 'SETTING::'src/core.c/control.pm6 line 269
Use of Nil in string context
  in sub warn at 'SETTING::'src/core.c/control.pm6 line 269
===> Failed to find dependencies: dot:from<bin>
Failed to resolve some missing dependencies (use e.g. --exclude="dot" to skip)

Similar topic as JJ/Raku-Doc-TypeGraph#33 ??? But here at least the dependency on graphviz is highlighted in the README... So, please do mention the same dependency also here :|

[2colours]

I wanted to say this repo is probably not meant to be installed anymore but then I saw this Raku/ecosystem@1d02e07 which says exactly that it's not meant to be installed.

[2colours]

https://raku.land/zef:coke/rakudoc this is the distribution that is meant to be installed.

[AntonOks]

https://raku.land/zef:coke/rakudoc this is the distribution that is meant to be installed.

Adding the latest committers, so @falsifian @Util @JJ @coke @2colours @tbrowder @niner

This is all good / valid feedback. Still there are "issues" opened for this module so people assume this module is still "alive".

If this module is considered to be "dead", someone should:

1. add an entry in the README, explaining this is an "unmaintained module" and pointing to the successor module, if any
2. set this repo into "archived mode"

[coke]

If you installed the dependencies (which are declared for testing only), you'd then run Build.rakudoc, which says:

This repository is not intended to be installed

This is not an unmaintained repository. It's just not meant to be installed as a module

[coke]

That said, I'll add a small note to the bottom of the README

[coke]

bottom

top

[2colours]

@AntonOks the README is always subject to improvements of course. :) But the general idea has become that this repository is for the content of documentation - and the vast majority of open issues are indeed about the content now, thanks to the quite persistent cleanup of Coke.