1 |
Ok, I may have jumped the gun a bit. I gave read all the documents at |
2 |
this point and read all the same bitches in the forums. I see reference |
3 |
to -vhost which is in theory the default. Maybe on an new install. Not |
4 |
on my existing installs. When the switch way made, it was done poorly. |
5 |
Previous implementations should have been honored. Instead, it appeared |
6 |
as though a user was forced to use webapp-config. Which I still believe |
7 |
is the case for the most part. I can adjust to the new stuff, but I |
8 |
think it needs some serious consideration from the portage devs as it |
9 |
breaks the use of portage. If this is the way of the future, I guess I'm |
10 |
stuck. Else, please consider moving back to making non-structural |
11 |
changes be handled by portage. |
12 |
|
13 |
Wendall |
14 |
|
15 |
On Thu, 2004-10-28 at 13:34, Wendall Cada wrote: |
16 |
> > The system should work in a way that such a separate install set is only |
17 |
> > necessary when virtual host support is enabled. (In which case it makes |
18 |
> > sense). If you have your system set up for single host webserving it is a bug |
19 |
> > if things are not installed automatically. |
20 |
> > |
21 |
> > Paul |
22 |
> |
23 |
> I use a virual hosting environment, and do not want to use or enable |
24 |
> webapp-config. I also don't think that it is a good criteria to base the |
25 |
> use of the tool from. I have not found a way to disable it. As soon as |
26 |
> all webapps were converted over to it, I have had to use it or nothing. |
27 |
> I think it should be setup by the user if they need the functionality |
28 |
> and left out by default if not. Let portage do the job it was designed |
29 |
> for and toolkits to do the jobs they were designed for. |
30 |
> |
31 |
> Wendall |
32 |
-- |
33 |
"Only the ideas that we really live have any value." --Hermann Hesse |
34 |
(Demian) |
35 |
|
36 |
|
37 |
-- |
38 |
gentoo-portage-dev@g.o mailing list |