| 1 |
On Dienstag 28 Juli 2009, Maximilian Bräutigam wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> recently, I have written an ebuild for the program sci-chemistry/gabedit |
| 5 |
> and published it at http://bugs.gentoo.org/show_bug.cgi?id=279438 |
| 6 |
> |
| 7 |
> I am a chemist, so please excuse the following questions. ;) |
| 8 |
> What will now happen with the published ebuild? Can I somehow help |
| 9 |
> getting it to portage? |
| 10 |
> |
| 11 |
> Is the bugreport configured correctly or did I make a mistake, due to |
| 12 |
> the fact that I am a noob in respect of writing ebuilds? I read many |
| 13 |
> docs about publishing and writing ebuilds, I checked the ebuild using |
| 14 |
> repoman, and really tried to do everything correctly. |
| 15 |
> |
| 16 |
> While checking the ebuild with repoman and reading the docs, I realized |
| 17 |
> that I have to create a ChangeLog and a metadata.xml. Do I have to post |
| 18 |
> them and the Manifest somewhere, too? |
| 19 |
> |
| 20 |
> Thank you very much in advance for your help. |
| 21 |
> |
| 22 |
> kind regards, |
| 23 |
> der Max |
| 24 |
|
| 25 |
well, bug wranglers will assign it to the right herd/dev and someone of that |
| 26 |
group will post his/hers comments. From that point on - you will see. |
| 27 |
|
| 28 |
I don't think that you need to attach a changelog - or manifest. Manifest is |
| 29 |
easily generated so that can IMHO wait until the final version that goes to the |
| 30 |
tree is found |
Archives