1 |
On Thursday 23 March 2006 20:43, Chris Bainbridge wrote: |
2 |
> On 23/03/06, Rumen Yotov <rumen@××××××.org> wrote: |
3 |
> > Hi, |
4 |
> > Using a remote overlays is rather simple, just do "emerge layman". |
5 |
> > Read the einfo and then "man layman". |
6 |
> > It works flawlessly, just tested this with one remote overlay. |
7 |
> > Beside that "man layman" explains pretty much of it's innerwork. |
8 |
> > PS:There's an article in "gentoo-wiki.com" with a list of overlays. |
9 |
> > HTH.Rumen |
10 |
> |
11 |
> What is the status of those overlays? I believe the php, webapps, and |
12 |
> java ones (at least) are official (in that they're run by gentoo devs) |
13 |
> and bugs are to be reported to bugs.g.o, no? But the wiki page |
14 |
> http://gentoo-wiki.com/Portage_Overlay_Listing says "NEVER report bugs |
15 |
> at bugs.gentoo.org for these ebuilds." So where should users report |
16 |
> bugs? And how are they to know that? |
17 |
Hi, |
18 |
From a very quick scan - yes there're some overlays made/supported by Gentoo |
19 |
devs and some others are hosted/maintained by users,so i think for the latter |
20 |
case you can't use Bugzilla in a sense that the ebuild is not in the tree. |
21 |
But looking from another angle (POV) if this is a new version ebuild or an |
22 |
ebuild for a new (not in the tree) package, why not report it's |
23 |
status/workings/bugs in Bugzilla, generally it'll be an usefull info. |
24 |
Like now when somebody files a Bug on a new version or makes and attaches |
25 |
initial ebuild for a new package. |
26 |
Of course all depends on the policy (if any is made) about this external |
27 |
(official & unofficial) overlays and Bugzilla. |
28 |
PS: you can yourself see/read there're big differences in opinion even between |
29 |
Gentoo devs conserning overlays. So a bug-report assigned to a dev who |
30 |
doesn't want to support overlays will probably get "WONTFIX" whatever. |
31 |
Rumen |