On Tue, Oct 4, 2022 at 4:34 PM Marcel Telka wrote:
> On Fri, Sep 30, 2022 at 07:16:18PM +0200, s...@pandora.be wrote:
> >
> > 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
On Fri, Sep 30, 2022 at 07:16:18PM +0200, s...@pandora.be wrote:
>
> 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
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:
For the specific case of library/python/mkdocs which is now obsolete,
changing/updating the docs.openindiana.org is a solution.
The webpage for documenation specifically says that most operating systems use:
"pip install mkdocs"
So by removing the documentation on "pkg install mkdocs" this
> 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:
"For OpenIndiana Hipster, MKDocs and all of it's dependencies have been
packaged and
On Thu, Sep 29, 2022 at 04:36:15PM +0200, Aurélien Larcher wrote:
> On Thu, Sep 29, 2022 at 4:30 PM Marcel Telka wrote:
>
> > On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote:
> > > We could define some rules or information depending on the nature of the
> > > package to mark
On Thu, Sep 29, 2022 at 04:36:15PM +0200, Aurélien Larcher wrote:
> At least maybe some indications on how to add the packages back and make
> sure there is no mistake or loss of consistency with the location/naming
> etc..
If anybody wants to re-add some obsoleted package back, or rebuild some
On Thu, Sep 29, 2022 at 4:30 PM Marcel Telka wrote:
> On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote:
> > We could define some rules or information depending on the nature of the
> > package to mark which dependencies are expected.
> > Some python modules have been added for
On Thu, Sep 29, 2022 at 04:18:01PM +0200, Aurélien Larcher wrote:
> We could define some rules or information depending on the nature of the
> package to mark which dependencies are expected.
> Some python modules have been added for the sake of resolving a dependency
> while others have no
On Thu, Sep 29, 2022 at 4:00 PM Marcel Telka wrote:
> On Thu, Sep 29, 2022 at 03:18:29PM +0200, Aurélien Larcher wrote:
> > I do not understand the need for obsoleting the entire package and
> removing
> > all the files instead of updating on the go.
> >
> > Could you explain the motivation?
>
>
On Thu, Sep 29, 2022 at 4:00 PM Marcel Telka wrote:
> On Thu, Sep 29, 2022 at 03:18:29PM +0200, Aurélien Larcher wrote:
> > I do not understand the need for obsoleting the entire package and
> removing
> > all the files instead of updating on the go.
> >
> > Could you explain the motivation?
>
>
On Thu, Sep 29, 2022 at 03:18:29PM +0200, Aurélien Larcher wrote:
> I do not understand the need for obsoleting the entire package and removing
> all the files instead of updating on the go.
>
> Could you explain the motivation?
There is no particular need. It is just simpler to obsolete than
On Thu, Sep 29, 2022 at 2:25 PM Marcel Telka wrote:
> Hi,
>
> Currently we provide Python versions 2.7, 3.5, 3.7, and 3.9 for
> OpenIndiana, while version 3.9 is the default version.
>
> Both Python 2.7 and 3.5 are no longer supported for two or almost three
> years now respectively - see
>
Hi,
Currently we provide Python versions 2.7, 3.5, 3.7, and 3.9 for
OpenIndiana, while version 3.9 is the default version.
Both Python 2.7 and 3.5 are no longer supported for two or almost three
years now respectively - see
https://devguide.python.org/versions/#versions for details, so we
18 matches
Mail list logo
