1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Jason Wever wrote: |
5 |
| That could be handled via some CONFIG_PROTECT foo (unless someone has a |
6 |
| more suitable method in mind) |
7 |
|
8 |
If I catch anyone trying to add CONFIG_PROTECT to |
9 |
/var/www/localhost/htdocs, I'll happily break their fingers. Portage's |
10 |
concept of CONFIG_PROTECT is totally unsuitable for anything inside this |
11 |
directory. If you want to see how to handle that properly, look at how |
12 |
webapp-config does it. |
13 |
|
14 |
| The new page is part of a whole new package itself, is a hard dependency |
15 |
| and contains no getting started type information. As for tasteful, some |
16 |
| of that is a matter of personal opinion (mine being that it isn't). |
17 |
|
18 |
Hrm ... we need to get all of those issues sorted then before the Apache |
19 |
refresh can be marked stable. Thanks for pointing it out. |
20 |
|
21 |
Best regards, |
22 |
Stu |
23 |
- -- |
24 |
Stuart Herbert stuart@g.o |
25 |
Gentoo Developer http://dev.gentoo.org/~stuart/ |
26 |
~ http://stu.gnqs.org/diary/ |
27 |
- -- |
28 |
-----BEGIN PGP SIGNATURE----- |
29 |
Version: GnuPG v1.4.1rc2 (MingW32) |
30 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
31 |
|
32 |
iD8DBQFCXvA/DC+AuvmvxXwRAhjCAKCY8SObNa/hec2EOFKTm3KI/rJYTACeIBzX |
33 |
GO3mQHO5lvQSSTJd2POGEO4= |
34 |
=6ta2 |
35 |
-----END PGP SIGNATURE----- |
36 |
|
37 |
-- |
38 |
gentoo-dev@g.o mailing list |