Packages

[Single Stage to Orbit]

This might be a stupid question, but is it possible to package up
things like compilers on an existing system to upgrade another system?

[Arne Vajhøj]

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package up
things like compilers on an existing system to upgrade another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

Arne

[Single Stage to Orbit]

Post by Arne Vajhøj

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package up
things like compilers on an existing system to upgrade another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

Oh, it's about the vmdk images that VSI sent out. I already have a
working system that I got under their previous hobbyist programme, jsut
wondered if it was possible to update my existing system by repackaging
stuff from the vmdk image and upgrading my system.

[John Reagan]

Post by Single Stage to Orbit

Post by Arne Vajhøj

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package up
things like compilers on an existing system to upgrade another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

Oh, it's about the vmdk images that VSI sent out. I already have a
working system that I got under their previous hobbyist programme, jsut
wondered if it was possible to update my existing system by repackaging
stuff from the vmdk image and upgrading my system.

From the vmdk? Probably not. A compiler install updates the CLD, the
HELP, and puts various files on the system (compiler, message files,
startup files, release notes, maybe RTLs), etc. In particular, the CLD
isn't just sitting around for all products. I would guess that VERB
could extract it however? But you don't know the exact list of things
to move/apply. That is all inside the PCSI/VMSINSTAL kit.

[Single Stage to Orbit]

Post by Single Stage to Orbit

Post by Arne Vajhøj

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package
up things like compilers on an existing system to upgrade
another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

Oh, it's about the vmdk images that VSI sent out. I already have a
working system that I got under their previous hobbyist programme,
jsut wondered if it was possible to update my existing system by
repackaging stuff from the vmdk image and upgrading my system.

From the vmdk?  Probably not.  A compiler install updates the CLD,
the HELP, and puts various files on the system (compiler, message
files, startup files, release notes, maybe RTLs), etc.  In
particular, the CLD isn't just sitting around for all products.  I
would guess that VERB could extract it however?  But you don't know
the exact list of things to move/apply.  That is all inside the
PCSI/VMSINSTAL kit.

I did suspect that might be the case. Oh well.

Maybe I can move my data off the system onto its own disk image and
then attach it to the vmdk image. Of course, I would need to configure
the vmdk image with its hostname and other things to make it useable
first.

Then every year I can just replace my vmdk with their latest that they
release, configure it and then attach my existing disk image.

That's a pain but workable. But I just wish they'd reinstate the
hobbyist programme. Some of us can find issues and report them quickly.

[Chris Townley]

Post by Single Stage to Orbit

Post by Single Stage to Orbit

Post by Arne Vajhøj

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package
up things like compilers on an existing system to upgrade
another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

Oh, it's about the vmdk images that VSI sent out. I already have a
working system that I got under their previous hobbyist programme,
jsut wondered if it was possible to update my existing system by
repackaging stuff from the vmdk image and upgrading my system.

From the vmdk?  Probably not.  A compiler install updates the CLD,
the HELP, and puts various files on the system (compiler, message
files, startup files, release notes, maybe RTLs), etc.  In
particular, the CLD isn't just sitting around for all products.  I
would guess that VERB could extract it however?  But you don't know
the exact list of things to move/apply.  That is all inside the
PCSI/VMSINSTAL kit.

I did suspect that might be the case. Oh well.
Maybe I can move my data off the system onto its own disk image and
then attach it to the vmdk image. Of course, I would need to configure
the vmdk image with its hostname and other things to make it useable
first.
Then every year I can just replace my vmdk with their latest that they
release, configure it and then attach my existing disk image.
That's a pain but workable. But I just wish they'd reinstate the
hobbyist programme. Some of us can find issues and report them quickly.

Have you thought of applying for Ambassador status?

[Single Stage to Orbit]

Post by Chris Townley

Post by Single Stage to Orbit
That's a pain but workable. But I just wish they'd reinstate the
hobbyist programme. Some of us can find issues and report them quickly.

Have you thought of applying for Ambassador status?

I did, a few months ago. Since the initial reply back, nothing.

[Dave Froble]

Post by Single Stage to Orbit

Post by Chris Townley

Post by Single Stage to Orbit
That's a pain but workable. But I just wish they'd reinstate the
hobbyist programme. Some of us can find issues and report them quickly.

Have you thought of applying for Ambassador status?

I did, a few months ago. Since the initial reply back, nothing.

Squeaky wheel sometimes gets the oil ...

[Craig A. Berry]

Post by Arne Vajhøj

Post by Single Stage to Orbit
This might be a stupid question, but is it possible to package up
things like compilers on an existing system to upgrade another system?

What would your package provide that the PCSI/VMSINSTAL kit does
not provide?

If he's got a community license, he doesn't have the PCSI/VMSINSTAL kit
but rather a new system image with a bunch of stuff already installed.
He would probably prefer not to set everything up again from scratch.

In theory, if one knew the locations of *all* of the pieces, one could
reverse engineer an older kit and build a new one like it with the new
images and data from an installation. But there are a lot of things
that could go wrong, depending on what changed between versions.

[Lawrence D'Oliveiro]

Post by Craig A. Berry
In theory, if one knew the locations of *all* of the pieces, one could
reverse engineer an older kit and build a new one like it with the new
images and data from an installation. But there are a lot of things
that could go wrong, depending on what changed between versions.

Seems like proprietary vendors do *not* have the incentive to support any
kind of modular package management.

[Scott Dorsey]

Post by Lawrence D'Oliveiro

Post by Craig A. Berry
In theory, if one knew the locations of *all* of the pieces, one could
reverse engineer an older kit and build a new one like it with the new
images and data from an installation. But there are a lot of things
that could go wrong, depending on what changed between versions.

Seems like proprietary vendors do *not* have the incentive to support any
kind of modular package management.

It's in their advantage to support package management for third-party
applications, because it makes it easier for third-party applications to
release and support their products.

It is against their advantage to support package management for the operating
system itself, because it will mean people will strip it down and no two
installations will be the same (as often happens with Linux) and this makes
support much more difficult. They sell all of these parts and they want you
to use them all together and never separate them. Not even to disable Clippy.
--scott