| 1 |
I'd say it depends, whether you think your ebuilds are so specific to |
| 2 |
prefix that they are only useful inside a prefix or whether you think |
| 3 |
they might be useful for gentoo/linux as well. |
| 4 |
|
| 5 |
As a rule of thumb, the long term goal is to get prefix "accepted" |
| 6 |
into mainline gentoo and merged into the main tree. The less changes |
| 7 |
or the less changes which are not scriptable by things like ecopy |
| 8 |
etc., the easier it is going to be to achieve this. Then again, I |
| 9 |
don't know how easy it is going to be to get stuff into the main tree. |
| 10 |
|
| 11 |
This is just my pov, though I hope to have summarized previous |
| 12 |
discussions here correctly. |
| 13 |
|
| 14 |
Tobias |
| 15 |
|
| 16 |
|
| 17 |
Am 22.04.2008 um 08:35 schrieb Qiangning Hong: |
| 18 |
> On Tue, Apr 22, 2008 at 12:03 PM, Jeremy <jer.gentoo@×××××.com> wrote: |
| 19 |
>> Generally just a unified diff of the eapified ebuild is all that is |
| 20 |
>> needed |
| 21 |
>> unless the changes are satisfied by a eapify or ecopy (ie trivial) |
| 22 |
>> then just |
| 23 |
>> knowing that is needed. Be sure to submit them to Product: "Gentoo/ |
| 24 |
>> Alt" and |
| 25 |
>> Component: "Prefix support" so they end up assigned to alt@g.o |
| 26 |
>> |
| 27 |
>> Be sure to check for deps too. |
| 28 |
> |
| 29 |
> I've write several ebuilds not exist in either main gentoo portage or |
| 30 |
> prefix overlay. Should I submit it to "Gentoo/Alt" product or submit |
| 31 |
> two bug reports to both "Gentoo/Alt" and "Gentoo Linux"? |
| 32 |
> |
| 33 |
> -- |
| 34 |
> Qiangning Hong |
| 35 |
> http://www.douban.com/people/hongqn/ |
| 36 |
> -- |
| 37 |
> gentoo-alt@l.g.o mailing list |
| 38 |
> |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-alt@l.g.o mailing list |
Archives