Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 107:17:18 |
Calls: | 290 |
Files: | 905 |
Messages: | 76,676 |
Just got an end of the year update from VSI, which was pretty routine
apart from one item.
VSI are talking about releasing a new version of GNV but I thought this
had long since become an external project hosted at SourceForge.
I checked the VSI website and they appear to have a single download of
the base kit, but only for Itanium, and which is located at:
https://vmssoftware.com/products/gnv/
So, is GNV a VSI or external project these days ?
On 12/23/2024 8:12 AM, Simon Clubley wrote:
Just got an end of the year update from VSI, which was pretty routine
apart from one item.
VSI are talking about releasing a new version of GNV but I thought this
had long since become an external project hosted at SourceForge.
I checked the VSI website and they appear to have a single download of
the base kit, but only for Itanium, and which is located at:
https://vmssoftware.com/products/gnv/
So, is GNV a VSI or external project these days ?
If you look at the installation link, then it points
to SourceForge, so it seems most likely that VSI takes
the SF code and make an official VSI version of that.
On 2024-12-23, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 12/23/2024 8:12 AM, Simon Clubley wrote:
Just got an end of the year update from VSI, which was pretty routine
apart from one item.
VSI are talking about releasing a new version of GNV but I thought this
had long since become an external project hosted at SourceForge.
I checked the VSI website and they appear to have a single download of
the base kit, but only for Itanium, and which is located at:
https://vmssoftware.com/products/gnv/
So, is GNV a VSI or external project these days ?
If you look at the installation link, then it points
to SourceForge, so it seems most likely that VSI takes
the SF code and make an official VSI version of that.
Interesting, but it doesn't explain why VSI are talking about creating
a new GNV version based on customer requests instead of just packaging
the SF version. I wonder if VSI are planning to fork the SF work.
On Mon, 23 Dec 2024 13:12:51 -0500, Arne Vajhøj wrote:
... if there are still VMS sites around with a strict
"only software from VMS owner or well known commercial vendors like
Oracle are allowed on the VMS system" policy.
I wonder how long customers with policies like that manage to stay in business ...
... if there are still VMS sites around with a strict
"only software from VMS owner or well known commercial vendors like
Oracle are allowed on the VMS system" policy.
Note though that unless you have some advanced security mechanisms in
place, then it may actually not be a bad policy. There has been a lot of malware attacks in recent years via reputable software repositories.
Note though that unless you have some advanced security
mechanisms in place, then it may actually not be a bad
policy. There has been a lot of malware attacks in
recent years via reputable software repositories.
Just got an end of the year update from VSI, which was pretty routine
apart from one item.
VSI are talking about releasing a new version of GNV but I thought this
had long since become an external project hosted at SourceForge.
I checked the VSI website and they appear to have a single download of
the base kit, but only for Itanium, and which is located at:
https://vmssoftware.com/products/gnv/
So, is GNV a VSI or external project these days ?
On 12/23/24 7:12 AM, Simon Clubley wrote:
Just got an end of the year update from VSI, which was pretty routine
apart from one item.
VSI are talking about releasing a new version of GNV but I thought this
had long since become an external project hosted at SourceForge.
I checked the VSI website and they appear to have a single download of
the base kit, but only for Itanium, and which is located at:
https://vmssoftware.com/products/gnv/
So, is GNV a VSI or external project these days ?
Both and neither. GNV originated within Compaq/HP(E) (possibly as part
of the COE project?) and the wrapper that more or less emulates the gcc command line with DEC/Compaq/HP(E) C is still a pretty close cousin of
what those folks built. That is one example, but most other parts also started with the vendor. Other people (mostly Eric Roberston, John
Malmberg, and Bill Pedersen) have taken individual pieces quite a bit
farther than anything that was coming out of HP. I'm hoping some of
those folks will chime in and correct/extend my comments.
VSI certainly needs a porting capability for code written elsewhere. I
have heard rumors of CMake for some years now but don't know the status.