From: heroxbd@gmail.com
To: gentoo-alt@lists.gentoo.org
Subject: [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix
Date: Wed, 03 Aug 2011 10:36:00 +0900 [thread overview]
Message-ID: <86ty9zxon3.fsf@gmail.com> (raw)
Dear Guys and Girls,
As a user of Gentoo Prefix, I even do not have a working Gentoo-x86.
When there is a need to include a new ebuild(including version bump),
according to techdoc[1], I need to file a bug against Gentoo-x86 and
wait for the changes to propagate to Prefix.
However nowadays, we have the Gentoo overlays for testing new ebuilds in
Gentoo-x86 before included in the main portage tree.
Therefore, if I want something new in Prefix without maintaining my own
ad-hoc dirty hack overlay, I will have to submit a bug and wait for it
to be included in one of Gentoo overlay, wait for it to be well tested
and mature enough to go into main portage tree, and wait for it to be
syncronized into Prefix. That is too long a cycle.
Furthermore, if I want to test the ebuilds that are just included in the
Gentoo overlay, there is no straight forward way in Prefix. Layman in
Prefix is different from that in Gentoo-x86.
To be more specific, in bug 346933[2], finally Andrew Savchenko has
merged my patch into science overlay for Gentoo-x86. What is the
recommended and consistant way to test that out when I only have (dozens
of) Gentoo Prefix at hand?
BTW, the cycle of a bug request of keywording a certain ebuild is also
too long. At present I maintain an overlay for myself for about 100
ebuilds only for adding an arch keyword to use in Prefix.
Hope I can find a way out of those. Suggestion and ideas are very
appreciated for me to enjoy more of my life with Prefix.
Yours,
Benda
1. http://www.gentoo.org/proj/en/gentoo-alt/prefix/techdocs.xml
2. https://bugs.gentoo.org/show_bug.cgi?id=346933
--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN
http://www.awa.tohoku.ac.jp/~benda
next reply other threads:[~2011-08-03 1:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 1:36 heroxbd [this message]
2011-08-03 5:49 ` [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix Zac Medico
2011-08-06 0:13 ` heroxbd
2011-08-06 0:42 ` Zac Medico
2011-08-06 1:24 ` heroxbd
2011-08-03 8:07 ` Fabian Groffen
2011-08-06 1:05 ` heroxbd
2011-08-06 7:37 ` Fabian Groffen
2011-08-10 1:17 ` heroxbd
2011-08-10 6:44 ` Fabian Groffen
2011-08-05 20:00 ` Jeremy Olexa
2011-08-10 1:31 ` heroxbd
2011-08-10 4:42 ` Jeremy Olexa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ty9zxon3.fsf@gmail.com \
--to=heroxbd@gmail.com \
--cc=gentoo-alt@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox