Lines 20-34
developers may not be familiar with.
Link Here
|
20 |
|
20 |
|
21 |
<p> |
21 |
<p> |
22 |
Before writing a new ebuild, check |
22 |
Before writing a new ebuild, check |
23 |
<uri link="http://bugs.gentoo.org/">bugs.gentoo.org</uri> |
23 |
<uri link="https://bugs.gentoo.org/">bugs.gentoo.org</uri> |
24 |
to see if an ebuild has already been written for the package, but has not yet |
24 |
to see if an ebuild has already been written for the package, but has not yet |
25 |
been added to the Portage tree. Go to <uri |
25 |
been added to the Portage tree. Go to <uri |
26 |
link="http://bugs.gentoo.org/">bugs.gentoo.org</uri>, choose query and select |
26 |
link="https://bugs.gentoo.org/">bugs.gentoo.org</uri>, choose query and select |
27 |
Advanced Search; as product select <e>Gentoo Linux</e>, as component select |
27 |
Advanced Search; as product select <e>Gentoo Linux</e>, as component select |
28 |
<e>ebuilds</e>. In the search field put the name of the ebuild and as status |
28 |
<e>ebuilds</e>. In the search field put the name of the ebuild and as status |
29 |
select NEW, ASSIGNED, REOPENED and RESOLVED (RESOLVED is important), then |
29 |
select NEW, ASSIGNED, REOPENED and RESOLVED (RESOLVED is important), then |
30 |
submit the query. For you lazy people, click <uri |
30 |
submit the query. For you lazy people, click <uri |
31 |
link="http://bugs.gentoo.org/query.cgi?product=Gentoo%20Linux&component=Ebuilds&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED">here</uri>. |
31 |
link="https://bugs.gentoo.org/query.cgi?product=Gentoo%20Linux&component=Ebuilds&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED">here</uri>. |
32 |
</p> |
32 |
</p> |
33 |
|
33 |
|
34 |
<p> |
34 |
<p> |
35 |
- |
|
|