Forum OpenACS Development: Is this a bug: right after creating pkg in APM, key is not known but should be

I believe creating a package via APM is consistent with retrieving packages from other locations, such as via CVS. Creating the package via APM creates the files and directories that are the framework for the package.

The next steps are:

2. "install" the package, which requires a server restart.

3. "mount" package in site-map (depending on package)

Separating the processes in this way allows multiple packages to be created with only one server restart, and helps to keep package generation consistent, since there is only one process for installing packages instead of two.

cheers,

Torben

I tried to be as specific as possible with the revised language by describing the actual actions taken, and suggesting a server restart to complete the install.. until a core developer could revise it appropriately.

http://fisheye.openacs.org/changelog/OpenACS/?cs=MAIN%3Atorbenb%3A20100407165017

The language change seems appropriate for the circumstances until a fix is made; and a fix should include revising it.

cheers,

Torben

1. The package version is set up and marked enabled and installed.

2. You go to the "install packages" acs-admin page, and the package does not show up.

3. Apparently it is half-installed/half-not installed.

4. The reason is that no apm_package_type is created for the package, so it's in a semi-zombie state (this is why you can't install it, and if it allowed you to install it, it would scream because the version already exists!)

Jim, you can test this by going to psql and giving this command:

select * from apm_package_versions where package_key = 'your-package-key';

and then

select * from apm_package_types where package_key = 'your-package-key'.

Torben, please remove your misleading change to the HTML page.

It would require a rewriting of the entire APM to get rid of this "install package upon creation" bit, because add depedencies, parameters, etc are all driven by the package version's params etc as stored in the database (not the XML info file).

So the right thing to do is to make the new package fully installed, as gross as that is, and I will do so this weekend, by making an entry in apm_package_types for the new package when it is created.

Does the apm_package_type mean (for now) service or app?