On Fri, 1 Apr 2005, Felipe de Jes�s Molina Bravo wrote: > so, I write this, because, I found a solution to my problem. And there > is how I solved it: > > #ebuild /path/of/mod_php.ebuild fetch > #ebuild /path/of/mod_perl.ebuild fetch > #ebuild /path/of/apache-1.3.33.ebuild fetch > > #ebuild /path/of/mod_php.ebuild unpack > #ebuild /path/of/mod_perl.ebuild unpack > #ebuild /path/of/apache-1.3.33.ebuild unpack > > Configure and compile, of course mod_php and mod_perl as static modules > for apache (read the install of mod_perl and mod_php) > > #touch .configure > for each work directoy (mod_php, mod_perl and apache) > in order to tell portage that mod_php,mod_perl and apache are compiled > > #ebuild apache install > > #ebuild apache qmerge
In other words you did a manual install. You may want to look at modifying the ebuild and making your own "local" ebuild for apache and mod_perl (just copy the existing ebuilds into a local copy under /usr/local/portage and modify them as needed, then set PORTAGE_OVERLAY in /etc/make.conf to activate it). It would make future custom installs easier for you and everything is still handled by using a single emerge command as normal. -- -- [email protected] mailing list
