1 |
On Tue, Apr 22, 2003 at 05:07:22PM -0500, Brian Jackson wrote: |
2 |
> Nobody showed an interest, but here it is anyway: |
3 |
> http://www.mdrx.com/brian/portage-local.tar.bz2 |
4 |
> There could be a lot more stuff there, and if anybody shows any interest, I |
5 |
> will probably try to setup an rsync server for people to pull from instead of |
6 |
> having to download and extract. |
7 |
I think this is actually a great idea for now, as an extra testing |
8 |
ground for some of the ebuilds. |
9 |
|
10 |
As a developer, I do occasionally merge a number of minor ebuilds that I |
11 |
need myself and are just sitting in the bugzilla tree, and then I keep |
12 |
an eye on them. |
13 |
|
14 |
The since most discougaging thing in any submitted ebuild is the lack of |
15 |
an included ChangeLog. To anybody submitting an ebuild, use |
16 |
skel.ChangeLog, and fill it out with the correct information. |
17 |
Additionally, for many of your ebuilds, in your posting about the bug |
18 |
specify what you did and why. It saves us a lot of trouble in |
19 |
testing the ebuild. Also make sure that your ebuild installs ALL of the |
20 |
documentation that is distributed with the source package. Take a look |
21 |
at /usr/share/doc and see how comprehensive some packages are in this |
22 |
regard. Don't forget the manpages either (a fairly common mistake). |
23 |
|
24 |
If you have a question about how to do something in an ebuild, look at |
25 |
other ebuilds or ask on this mailing list. |
26 |
|
27 |
If there is an ebuild that is totally ready to go out (eg I _could_ just |
28 |
dump the files into a new directory and check them in. I don't for |
29 |
security and QA reasons) of the box, it |
30 |
greatly increases the chance that it will get into the tree quickly. |
31 |
Very few submitted ebuilds come up to this level. I will admit that it |
32 |
is a lot to ask for, but it really makes life as a developer much |
33 |
easier. |
34 |
|
35 |
Personally, for any ebuild I am willing to pick up, I generally do the |
36 |
following: |
37 |
0. read the submitted ebuild AND changelog |
38 |
1. grab the source tarball |
39 |
2. read the included documentation |
40 |
3. read the documentation on the web and other information I can find |
41 |
about it |
42 |
4. re-read the included documentation |
43 |
5a. attempt to compile it only inside a sandbox enviroment |
44 |
5b. if problems from 5a, look at some of the source code/ebuild to |
45 |
figure out why |
46 |
6. see what 'make install' or the other standard methods of install |
47 |
WOULD install and compare that to the ebuild install instructions. |
48 |
7. install it on a testbed system and do some simplistic functionality |
49 |
and security (trojaning) checks |
50 |
8. install it on 3-5 other systems with widely varying configurations to |
51 |
see if it installs cleanly in most cases. |
52 |
9. commit to CVS |
53 |
|
54 |
Generally this process is spread anywhere between 6 hours and a week |
55 |
long, depending on package complexity and how busy I am with |
56 |
work/school and my other open source work (I'm a developer on |
57 |
phpMyAdmin). |
58 |
|
59 |
19 times of of 20, if a submitted ebuild is more complex than |
60 |
emake/einstall and doesn't include a changelog or some detailed comments |
61 |
inside the ebuild as to what is being done, then I don't touch it. |
62 |
|
63 |
Definetly having more developers/maintainers would help, but there are |
64 |
many issues around this (as people have pointed out in the thread). |
65 |
Debian's "solution" to many of the problems was a dedicated maintainer |
66 |
for each package, and only a few packages per maintainer to keep things |
67 |
managable, but that requires a LOT of maintiners/developers. There are |
68 |
some changes under discussion for Gentoo on this presently, but I won't |
69 |
say more now, as not to get people's hopes up for the outcome as it |
70 |
could change a lot. |
71 |
|
72 |
-- |
73 |
Robin Hugh Johnson |
74 |
E-Mail : robbat2@××××××××××××××.net |
75 |
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 |
76 |
ICQ# : 30269588 or 41961639 |
77 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |