"Alvin B. Marcelo" wrote:
> 
> >It would be good to have more specifics here (off-line).  Many of the
> >prerequisites are available from a subdirectory of the distribution
> >location.
> 
> I'll give the specifics online Brian as I may be at fault here. Call me
> lazy but I don't usually go to subdirectories to look for something I don't
> know is there. The Circare implementation guide is great. And as a newbie,
> I prefer step by step guides (the implementation seems to be just that).
> 
> Yet, I got stumped at step: Prerequisites
> http://www.minoru-development.com/circare/implement/impl.html#2_1
> 
> since I assumed I would have to download and install each one from the
> parent site of the components (which ideally I should). This is because the
> enumerated components are linked to the mother sites. Should they be linked
> to the subdirectory?
> 
> Bottomline: this user (maybe there are more out there like me?) considers
> installation success as inversely proportional to the number of components
> required. Failure rate increases when one of the component sites become
> bogged down for some reason.
> 
> Note that these comments are generally about open source application
> development and promotions and not about any application in particular. We
> should try our best to minimize dependencies (either by integrating them
> into one package like RPMs or providing access to multiple sources of the
> code).
> 
> I am still bent on installing all the projects for comparison (of course,
> apples to apples)...
> 
> Alvin

Thanks for the comments.

I'll add a note to the implementation guide stating that copies of the
prerequisites (for RedHat) are available in the subdirectory.

This is a general problem with prerequisites.  At the time these
components were chosen, it looked like everything except the BW
application framework would be part of a standard Linux distribution.
The problem areas are MICO and unixODBC.  These are in some
distributions, but not all.  There are sometimes problems with version
compatibility.

The same thing is true for many other projects and their prerequisites.

This problem is the "flip side" of not re-inventing the wheel.  If you
make use of an existing open source package, then it becomes a
prerequisite for your own install.

-Brian

Reply via email to