| 1 |
On Sat, 2 Apr 2011 03:24:04 +0000 (UTC), Grant Edwards wrote: |
| 2 |
|
| 3 |
> >> How do I convince portage that viewvc does not require an external |
| 4 |
> >> web server and I don't want apache or webappconifg installed? |
| 5 |
> > |
| 6 |
> > It's a web app, |
| 7 |
> |
| 8 |
> Yes, it can be a "web app". It can also be run stand-alone using its |
| 9 |
> own web server with no external dependancies other than python and |
| 10 |
> support for the VC system you want to use. |
| 11 |
|
| 12 |
I see. |
| 13 |
|
| 14 |
> > Try putting apache in /etc/portage/profile/package.provided. |
| 15 |
> |
| 16 |
> That seems like a kludge that's likely to cause problems later. |
| 17 |
|
| 18 |
It is :( |
| 19 |
|
| 20 |
> ISTM |
| 21 |
> that the ebuild is broken. I'll have to take a shot at fixing the |
| 22 |
> ebuild so it doesn't depend on apache and webapp-config unless you |
| 23 |
> install it USE flags telling it you want it to use apache and |
| 24 |
> webapp-config. |
| 25 |
> |
| 26 |
|
| 27 |
From a quick glance at the webapp eclass, it looks like you need |
| 28 |
to set WEBAPP_OPTIONAL="yes" in the ebuild. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Neil Bothwick |
| 33 |
|
| 34 |
Fer sail cheep, Windows spel chekcer, wurks grate |
Archives