I'd say it depends, whether you think your ebuilds are so specific to
prefix that they are only useful inside a prefix or whether you think
they might be useful for gentoo/linux as well.
As a rule of thumb, the long term goal is to get prefix "accepted"
into mainline gentoo and merged into the main tree. The less changes
or the less changes which are not scriptable by things like ecopy
etc., the easier it is going to be to achieve this. Then again, I
don't know how easy it is going to be to get stuff into the main tree.
This is just my pov, though I hope to have summarized previous
discussions here correctly.
Tobias
Am 22.04.2008 um 08:35 schrieb Qiangning Hong:
On Tue, Apr 22, 2008 at 12:03 PM, Jeremy <[EMAIL PROTECTED]> wrote:
Generally just a unified diff of the eapified ebuild is all that is
needed
unless the changes are satisfied by a eapify or ecopy (ie trivial)
then just
knowing that is needed. Be sure to submit them to Product: "Gentoo/
Alt" and
Component: "Prefix support" so they end up assigned to [EMAIL PROTECTED]
Be sure to check for deps too.
I've write several ebuilds not exist in either main gentoo portage or
prefix overlay. Should I submit it to "Gentoo/Alt" product or submit
two bug reports to both "Gentoo/Alt" and "Gentoo Linux"?
--
Qiangning Hong
http://www.douban.com/people/hongqn/
--
[email protected] mailing list
--
[email protected] mailing list
