1 |
Dear Guys and Girls, |
2 |
|
3 |
As a user of Gentoo Prefix, I even do not have a working Gentoo-x86. |
4 |
|
5 |
When there is a need to include a new ebuild(including version bump), |
6 |
according to techdoc[1], I need to file a bug against Gentoo-x86 and |
7 |
wait for the changes to propagate to Prefix. |
8 |
|
9 |
However nowadays, we have the Gentoo overlays for testing new ebuilds in |
10 |
Gentoo-x86 before included in the main portage tree. |
11 |
|
12 |
Therefore, if I want something new in Prefix without maintaining my own |
13 |
ad-hoc dirty hack overlay, I will have to submit a bug and wait for it |
14 |
to be included in one of Gentoo overlay, wait for it to be well tested |
15 |
and mature enough to go into main portage tree, and wait for it to be |
16 |
syncronized into Prefix. That is too long a cycle. |
17 |
|
18 |
Furthermore, if I want to test the ebuilds that are just included in the |
19 |
Gentoo overlay, there is no straight forward way in Prefix. Layman in |
20 |
Prefix is different from that in Gentoo-x86. |
21 |
|
22 |
To be more specific, in bug 346933[2], finally Andrew Savchenko has |
23 |
merged my patch into science overlay for Gentoo-x86. What is the |
24 |
recommended and consistant way to test that out when I only have (dozens |
25 |
of) Gentoo Prefix at hand? |
26 |
|
27 |
BTW, the cycle of a bug request of keywording a certain ebuild is also |
28 |
too long. At present I maintain an overlay for myself for about 100 |
29 |
ebuilds only for adding an arch keyword to use in Prefix. |
30 |
|
31 |
Hope I can find a way out of those. Suggestion and ideas are very |
32 |
appreciated for me to enjoy more of my life with Prefix. |
33 |
|
34 |
Yours, |
35 |
Benda |
36 |
|
37 |
1. http://www.gentoo.org/proj/en/gentoo-alt/prefix/techdocs.xml |
38 |
2. https://bugs.gentoo.org/show_bug.cgi?id=346933 |
39 |
-- |
40 |
XU Benda |
41 |
Research Center for Neutrino Science |
42 |
Tohoku University |
43 |
JAPAN |
44 |
|
45 |
http://www.awa.tohoku.ac.jp/~benda |