1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Dylan Carlson wrote: |
5 |
| Here here. |
6 |
| |
7 |
| Regardless of what we agree the pathname should be, it's a good idea. |
8 |
| |
9 |
| I'd also like to see a naming convention of patches established. (crowd |
10 |
| moans: "not more red tape!") OK, perhaps more of a guideline/best |
11 |
| practices than a requirement. Right now I don't believe there is one... |
12 |
| is there? It would be refreshing to look at that patch repository and |
13 |
see |
14 |
| clarity and consistency in naming, as that will be a large listing of |
15 |
| files. |
16 |
|
17 |
I agree, this would be a very good policy to put into place. Removing |
18 |
all of the patches from the tree will help to reduce its size, by how |
19 |
much has already been a topic of debate, but it would help regardless. |
20 |
If it doesn't make that big of a difference now, it has the potential of |
21 |
stopping this from becoming a bigger problem in the future. |
22 |
|
23 |
The tree is growing at a very large rate and rsync times are taking a |
24 |
lot longer now than they did for me a year or so ago. Removing all of |
25 |
the patches from the tree will definitely help this, but I think other |
26 |
policies should be more strictly inforced as well. There are some very |
27 |
large files in the tree currently that aren't patches, like enormous |
28 |
Changelogs for a few packages, and also a lot of old ebuilds that are |
29 |
sitting around for some packages. It'd be nice if the tree was kept as |
30 |
clean as possible to keep rsync times down as much as possible. |
31 |
|
32 |
Mark |
33 |
-----BEGIN PGP SIGNATURE----- |
34 |
Version: GnuPG v1.2.6 (GNU/Linux) |
35 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
36 |
|
37 |
iD8DBQFBbuoHZPlCVB9SdGIRApTpAJ92YzwcPjge6QMofhdpnmx9Z0BpuACdFMK6 |
38 |
AtTFt0hR3utggvOnar7cBU0= |
39 |
=85Ee |
40 |
-----END PGP SIGNATURE----- |
41 |
|
42 |
-- |
43 |
gentoo-dev@g.o mailing list |