The versions get set by the pkg5 build process, you shouldn't need to
do anything. If you need to do it for your own testing, it's the
PKGVERS variable in src/pkg/Makefile
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/li
I'm preparing a PR for the pkg5 component of OI. This PR only modifies
the pkgrecv.1 man page file. The upstream source is:
https://github.com/OpenIndiana/pkg5
How do I ensure that the resulting OI package will have a newer
version number? With native OI packages, I'd do it by incrementing
>
> 1) Migrate away from 3.5 to 3.7 as the default Python implementation.
>
First steps of the week, the following modules were updated and support for
Python 3.7 and 3.9 was added:
argcomplete
atomicwrites
attrs
chardet
coverage
funcsigs
hypothesis
idna
importlib-metadata
incremental
ipaddress
m
Hello,
out or curiosity, what exactly is the point and added of your proposed fork?
Those packages can be easily installed any time after installing OI.
I am not sure which exact changes were rejected, but if your raise a discussion
and explain clearly why they are needed, OI developers are mor
Someone on this list challenged me of forking OpenIndiana in order for my
changes to be accepted. This is exactly what I'm going to do now. But I will do
it moderately, according to my skills.
I wanted to build something like in the title.
It's the normal desktop OI plus the following packages:
