FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Alt

 
 
LinkBack Thread Tools
 
Old 08-03-2011, 01:36 AM
 
Default Best Practice in Adopting New Ebuilds in Prefix

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
 
Old 08-03-2011, 05:49 AM
Zac Medico
 
Default Best Practice in Adopting New Ebuilds in Prefix

On 08/02/2011 06:36 PM, heroxbd@gmail.com wrote:
> 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.

This is totally unnecessary, since you can use
$EPREFIX/etc/portage/package.accept_keywords for these. Also, it's
common to use emerge's --autounmask-write option to populate this file
automatically.
--
Thanks,
Zac
 
Old 08-03-2011, 08:07 AM
Fabian Groffen
 
Default Best Practice in Adopting New Ebuilds in Prefix

On 03-08-2011 10:36:00 +0900, heroxbd@gmail.com wrote:
> 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.

Show us your capabilities, and become a Gentoo Developer in particular
for the Gentoo Prefix project, and help us out to improve our
understaffed project.

There is absolutely nothing that blocks your contributions but time of
the main developers, like me.

Thanks,

--
Fabian Groffen
Gentoo on a different level
 
Old 08-05-2011, 08:00 PM
Jeremy Olexa
 
Default Best Practice in Adopting New Ebuilds in Prefix

On Wed, 03 Aug 2011 10:36:00 +0900, heroxbd@gmail.com wrote:

< .... >
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.


Correct you are. Without boring you of historical details, the
layman-2* ebuilds should be hitting the mirrors soon that more align us
with gentoo-x86. Moving forward, there will not be a seperate Gentoo
Prefix layman list of overlays.


-Jeremy
 
Old 08-06-2011, 12:13 AM
 
Default Best Practice in Adopting New Ebuilds in Prefix

Dear Zac,

Zac Medico <zmedico@gentoo.org> writes:

> This is totally unnecessary, since you can use
> $EPREFIX/etc/portage/package.accept_keywords for these.

Ah-ha, from GLEP22[1], e.g. ~amd64 is a default to ~amd64-linux. Why
don't we just treat these reasonable defauls as equal in the portage?

I see bugs (and submit myself) in bugzilla to add keywords as
~amd64-linux when there is already ~amd64. Wondering the motivation of
doing it explicitly.

> Also, it's common to use emerge's --autounmask-write option to
> populate this file automatically.

O, I would give it a try.

Regards,
Benda

1. http://www.gentoo.org/proj/en/glep/glep-0022.html

--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN

http://www.awa.tohoku.ac.jp/~benda
 
Old 08-06-2011, 12:42 AM
Zac Medico
 
Default Best Practice in Adopting New Ebuilds in Prefix

On 08/05/2011 05:13 PM, heroxbd@gmail.com wrote:
> Dear Zac,
>
> Zac Medico <zmedico@gentoo.org> writes:
>
>> This is totally unnecessary, since you can use
>> $EPREFIX/etc/portage/package.accept_keywords for these.
>
> Ah-ha, from GLEP22[1], e.g. ~amd64 is a default to ~amd64-linux. Why
> don't we just treat these reasonable defauls as equal in the portage?

You can configure that yourself by setting ACCEPT_KEYWORDS="~amd64
amd64" in make.conf.

However, it's not generally recommended since when ~amd64-linux is
missing from KEYWORDS it means that it may not have been tested in a
amd64-linux prefix environment. Sometimes it will work, but it's also
common for such ebuilds to try and install files outside of $EPREFIX
which will cause them to abort before they are installed.

Also, if you use package.accept_keywords along with --autounmask-write,
then you'll have a list of packages that is convenient if you plan to
submit keyword requests.

> I see bugs (and submit myself) in bugzilla to add keywords as
> ~amd64-linux when there is already ~amd64. Wondering the motivation of
> doing it explicitly.

In order to indicate that it has been tested in a prefix environment,
versus a non-prefix environment.
--
Thanks,
Zac
 
Old 08-06-2011, 01:05 AM
 
Default Best Practice in Adopting New Ebuilds in Prefix

Hello Fabian,

Fabian Groffen <grobian@gentoo.org> writes:

> Show us your capabilities, and become a Gentoo Developer in particular
> for the Gentoo Prefix project, and help us out to improve our
> understaffed project.

That's great. I'd love to. I am have been using Gentoo Prefix for more
than 1 year, and Debian for ~7 years. For programming I had (learning)
experiences for Python/Perl/C/Lisp, though in my academic work Python is
used most often. I have been always been a user in the community and now
willing to have a try to contribute as a developer. As a graduate
student, I have at least 4 hours of spare time usually everyday (except
for the exams, thesis/report deadlines, etc.).

I guess becoming a developer particular for Gentoo Prefix is somewhat
different than that of gx86, in that I don't need to do those practice
in the overlays?

Where should I start from now? Maybe this quiz[1]?

> There is absolutely nothing that blocks your contributions but time of
> the main developers, like me.

Right. For me, I just need some guidance to set things up and go. Hope
people around the list can help me through the process.

Yours,
Benda

http://dev.gentoo.org/~grobian/prefix-quiz
--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN

http://www.awa.tohoku.ac.jp/~benda
 
Old 08-06-2011, 01:24 AM
 
Default Best Practice in Adopting New Ebuilds in Prefix

Hi Zac,

Zac Medico <zmedico@gentoo.org> writes:
> <....>
> Also, if you use package.accept_keywords along with --autounmask-write,
> then you'll have a list of packages that is convenient if you plan to
> submit keyword requests.

I see! Now I get the point. Yeah, it's much more convenient than what I
did. Thank you for your explanation, which cleared many of vague puzzles
in my head for a long time.

Yours,
Benda
--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN

http://www.awa.tohoku.ac.jp/~benda
 
Old 08-06-2011, 07:37 AM
Fabian Groffen
 
Default Best Practice in Adopting New Ebuilds in Prefix

Hi Benda,

On 06-08-2011 10:05:40 +0900, heroxbd@gmail.com wrote:
> I guess becoming a developer particular for Gentoo Prefix is somewhat
> different than that of gx86, in that I don't need to do those practice
> in the overlays?
>
> Where should I start from now? Maybe this quiz[1]?

There is no difference in the recruitment (and status) between
Prefix-enabled developers and normal Gentoo developers.
(I made that Prefix-enabled up, right here ... )

You'll have to go through the normal Gentoo recruitment process [2], and
before I grant you access to the prefix overlay [3], I ask you to fill
in my Prefix quiz [1], so you learn about certain things that are often
go wrong.

We'll find someone to mentor you, you don't have to do that yourself.

> [1] http://dev.gentoo.org/~grobian/prefix-quiz
[2] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
[3] http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay


--
Fabian Groffen
Gentoo on a different level
 
Old 08-10-2011, 01:17 AM
 
Default Best Practice in Adopting New Ebuilds in Prefix

Dear Fabian,

After reading through the recruitment process[1], I think the process
for me is like this. Correct me if I misunderstood something.

1. I will have a mentor (one of the Prefix developer?) and he would open
a bug for me.

2. I send the ebuild quiz to my mentor and the Gentoo recruiters
recruiters@gentoo.org

3. After the normal Gentoo recruitment process is finished. At this
point I am a Gentoo developer (oy~). Then I take the Prefix quiz for
prefix tree access (or I can do the two in parallel?)

So now I need to figure out who would be my mentor.

Thanks a lot!

Yours,
Benda
--
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN

http://www.awa.tohoku.ac.jp/~benda
 

Thread Tools




All times are GMT. The time now is 12:17 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org