Forum OpenACS Development: Awesome 5.0 SW Install - Almost Works!
o go to /acs-admin/install
o follow the "Install new application" link under "Install from OpenACS Repository" heading.
o place a checkmark on Weblogger
o click "Install checked applications"
An error indicating that a prerequisite package is not install which is to be expected (unless it were to add the prerequisite packages automatically... but that should be another thread). The missing prerequisite in this case is "trackback".
What isn't expected is the list of packages that are displayed that were not selected on the previous page:
Date and Time Utilities
Weblogger 1.0d1 Requires trackback 0.1d
OK. So, in response to the message text:
o hit the Back button
o the package that now shows as being selected is "User Profile" which happens to be the package just above "Weblogger" in the selection table.
o now, for fun, click the Forward button and then the Back button
o the package that shows as being selected is now "Ticket Tracker Lite" which happens to be the package above "User Profile"
o hit Forward then Back a few times and the selection will migrate upward one position for each Forward/Back pair.
Could someone add the trackback package to the repository?
The selection migration issue is a real bug.
Also, beware that the repository currently sits on one of our development servers, and is only current as of that date!
I'm in the process of generalizing and migrating the script to build the repository of APM files to openacs.org.
Next step: up2date for OpenACS :)
http://openacs.org/bugtracker/openacs/bug?bug%5fnumber=1103 is filed under ACS Admin.
Wow! Looks like .LRN and 5.0 bugs are _really_ pouring in...
Once again I have to say that the stuff Lars & Co. have added to 5.0 is _awesome_! Thanks guys (and gals)! Stand up and take a bow!
I know there are lots of other contributors, but I keep bumping into Lars.
For released stuff, it only needs to be built once the release is ... released.
For HEAD version, it should be rebuilt every night.
I haven't bothered too much with the code to building the repository yet, since we can always improve on that after the release is out, it's only going to sit on openacs.org.
The code to build the repository is in acs-admin/www/apm/build-repository.tcl - it's not linked from the UI, since it should generally only be run on openacs.org. If you want to host your own package repository, though, you can.
I've put up a repository for HEAD at http://openacs.org/repository/5-0/manifest.xml.
I haven't configured it to automatically rebuild, so the HEAD packages will stay current as of about 1 hour ago until we release 5.0.
A follow up question (or perhaps a bug) on the nightly build of openacs.org/repository/5-0/manifest.xql. Even though cvs.openacs.org/contrib/packages/bcms/bcms.info 1.3 states that the packages is at version .3 and HEAD is listed as one of the tags, the manifest reads .2. Looks to me like a tagging/branching issue. cvs.openacs.org/contrib/packages/bcms/bcms.info 1.2 is at .2 and it is also the branching point for oacs-5-0.
Is this correct behavior for the manifest?
Lars did a "one time" build (dated above) of the repository. As far as I know, the repository is not being rebuilt, though it's probably time to set this up. I, for one, would like to use the install-from-repository feature. In fact, I do use it for quick looks at packages and then do a regular CVS co if I want to work with the package.
At a minimum, we need to build the repository on every release, e.g. 5.0.0, 5.0.1, etc.
Alternatively, we can auto-build it every night, although if you're not on a release (and we don't have one yet), you shouldn't be using repository-install.
And if you are on a release, then the contents of the repository will only change when the next release.