| 1 |
Not to generate useless traffic, but I feel it is very important to |
| 2 |
reiterate this. |
| 3 |
|
| 4 |
Please, please, please attach your ebuilds to bugzilla as text/plain and |
| 5 |
as single files. Two common errors I have seen plenty are attaching a |
| 6 |
.tar.gz or .tar.bz2, or, and more of a problem for me, are the text |
| 7 |
files attached, but set as an octet stream so the viewer wont kick in. |
| 8 |
|
| 9 |
This cant be stressed enough as the 'proper' way to submit an ebuild if |
| 10 |
you want to see it committed as fast as possible. |
| 11 |
|
| 12 |
And as an aside, maybe zhen or whoever maintains bugs.g.o can set |
| 13 |
text/plain as the default file upload, because i assume plenty of people |
| 14 |
just forget to change it. |
| 15 |
|
| 16 |
--Todd |
| 17 |
|
| 18 |
On Fri, 2003-05-30 at 10:33, Alastair Tse wrote: |
| 19 |
> On Fri, 2003-05-30 at 15:22, MAL wrote: |
| 20 |
> > Is it better to upload an ebuild as a .tar.bz2 with digests, patches |
| 21 |
> > etc. all included? |
| 22 |
> |
| 23 |
> Ebuilds should not be attached as tar.bz2, they should be in text/plain. |
| 24 |
> It's actually written in the Ebuils Contribution Guide somewhere, and |
| 25 |
> also one of the most common problems with ebuild submission as I listed |
| 26 |
> in my ebuild mistakes list |
| 27 |
> (http://cvs.gentoo.org/~liquidx/ebuildmistakes.html). |
| 28 |
> |
| 29 |
> Cheers, |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives