On Tue, Dec 09, 2003, [EMAIL PROTECTED] wrote:

> As I ever used the prebuild apache package from the distro I used, and extra
> apache modules where offen separate packages (like mysql, php, perl), I'm not
> shure how to proceed with OpenPKG.
> looking at rpm -qpi apache-1.3.28-1.3.2.src.rpm it seema to me that all modules
> have to be build just when building apache.
> Is that so, or can I later add functionalitys to apache just ading a new module ?
> 
Although Michael explained a sophisticated workaround i want to point
out that "the OpenPKG way of doing it" is to use static libraries
which get embedded in the application at compile time. If you want to
change an option, you need to rebuild. I don't want to go into deeper
details because we will end up in a general static vs. shared library
discussion. Maybe http://www.openpkg.org/faq.html#no-shlib in the FAQ
will help you understanding the philosophy.

--
[EMAIL PROTECTED], Cable & Wireless
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to