I think that the idea is to keep using "mkdocs 1.0.4' for the moment due to
some Theme issue.
According to the website https://www.mkdocs.org/about/release-notes/ the
current release is mkdocs 1.4.0 which is not tested/required for OpenIndiana
documentation.
However the good news is that
On Fri, 30 Sep 2022, s...@pandora.be wrote:
For example in my Vagrantfile I have a comment about a missing 2.7 'futures'
component:
https://github.com/OpenIndiana/vagrantfiles/blob/main/oi-docs/Vagrantfile
# there used to be a futures package in the repo ...
#
Part of the problem is, I think, that there is no maintainer any longer, as far
as I know, for the mkdocs component in oi-userland.
If someone knows how to build mkdocs with python 3 (which is perhaps possible,
I don't know, I have no experience with building python components) then this
I sometimes submit documentation updates but I don't know the exact background
or history of mkdocs on OpenIndiana.
See for the discussion on "what should happen with mkdocs":
https://github.com/OpenIndiana/oi-docs/issues/226
There were several contributors who are in favor of using "pip
On Thu, Sep 29, 2022 at 06:46:40PM +0200, s...@pandora.be wrote:
>
> > Based on the rule above we already obsoleted following packages
> > recently:
> >
> ...
> > library/python/mkdocs
> ...
>
> see http://docs.openindiana.org/contrib/getting-started/
>
> that page says for installing mkdocs:
