I found that one, and (at least here) it will not install on 5.2.
This is one of the issues with code organization that I mentioned on this thread http://www.openacs.org/forums/message-view?message_id=337852
How in the heck is one supposed to figure this out without some organizational structure in the code? One might imagine that this would have been named dotlrn-portal at least.
It is pretty obvious that the package called "new-portal" is not going to get any documentation anytime soon, given the length of time that it has remained undocumented. So, without some codebase structure, one would never know.
I've been searching the forums for quite a while, and until Nick's message, there was never an explicit statement that new-portal is only for dotlrn. Now, I'm sure that I'll get 20-30 references to just that now :)
I'm far away from Boston, but I'm vaguely aware that Sloan paid for a goodly bit of development here in the process of building dotlrn. So, I'm mindful of biting the hand that feeds. But it is ever so clear to me that dotlrn needs a separate place in the code hierarchy. And that oacs needs to support a directory of related packages as a group in APM. That way it can be added or not as a piece, and it will be very clear where dependencies are.
Cheers!
-sam
