| 1 |
> On Wednesday 07 February 2007 23:19:53 Daevid Vincent wrote: |
| 2 |
> > Honestly, I really don't see how they're even remotely |
| 3 |
> related. So either |
| 4 |
> > I'm just dense, or the maintainer is not understanding my |
| 5 |
> request... It's |
| 6 |
> > extremely frustrating. |
| 7 |
> > |
| 8 |
> > [Bug 165709] When viewing "emerge -avu world" show which |
| 9 |
> packages are |
| 10 |
> > stable (or ~x86) |
| 11 |
> > |
| 12 |
> > http://bugs.gentoo.org/show_bug.cgi?id=165709 is my original one |
| 13 |
> > |
| 14 |
|
| 15 |
> So... it will be a lot easier for me to tell you what your |
| 16 |
> options are wrt. |
| 17 |
> working around this bug if you post the output of: |
| 18 |
> |
| 19 |
> # emerge -Dup world --tree --verbose |
| 20 |
|
| 21 |
Thanks, but I don't have a bug to solve here. Just the feature request. |
| 22 |
|
| 23 |
> Wrt. bug #165709 I'd probably have pointed you towards |
| 24 |
> app-portage/eix and |
| 25 |
> resolved it as WONTFIX or even INVALID as I really don't see |
| 26 |
> the point in |
| 27 |
> that feature request. There are a lot of tools including eix |
| 28 |
> that are a lot |
| 29 |
> more suitable for queries about what is stable and what isn't. I do |
| 30 |
> understand jakubs reasoning for thinking it's triggered by |
| 31 |
> bug #157361 and |
| 32 |
> hence marking it a dupe of that though. |
| 33 |
|
| 34 |
Yes, but then I have to manually, one at a time search eix and compare to |
| 35 |
the output of 'emerge world'. I use eix. That's actually why I suspect that |
| 36 |
the feature could be implemented fairly easily. Portage has all the info it |
| 37 |
needs. |
| 38 |
|
| 39 |
> I think reopening the same bug 3 times is a terrible idea. It |
| 40 |
> clearly doesn't help anyone. |
| 41 |
|
| 42 |
Nor does just blindly closing it without really comprehending what the |
| 43 |
request is for. |
| 44 |
|
| 45 |
> The most obvious options after the first time |
| 46 |
> are to CC the |
| 47 |
> dev-portage@g.o alias on the bug to make the portage |
| 48 |
> devs aware of it |
| 49 |
> (while commenting about why you do that), or to post a mail |
| 50 |
> here, on the |
| 51 |
> gentoo-dev-portage@ mailing list (this is a feature request |
| 52 |
> for portage after |
| 53 |
> all) or log onto irc and talk to the portage devs in |
| 54 |
> #gentoo-portage on freenode. |
| 55 |
|
| 56 |
Actually, I'll just concede defeat. :( |
| 57 |
|
| 58 |
Obviously the maintainer has either a closed mind and is unwilling to |
| 59 |
consider my request, or he just doesn't "get it" and wants to lump two |
| 60 |
disjointed bugs together. |
| 61 |
|
| 62 |
I get the feeling that even after all the work to get it into an "official" |
| 63 |
bug/request. I'll either be greeted with "learn python and code it yourself |
| 64 |
as a patch", or it will sit there forever amongst the thousands of other |
| 65 |
bugs... |
| 66 |
|
| 67 |
Mostly by posting here, I just wanted to know if I was missing something |
| 68 |
obvious and being a retard or if the maintainer was... *sigh* ...also that |
| 69 |
maybe someone else would say, "oh yeah, I like that idea" and perhaps could |
| 70 |
articulate it better than I... |
| 71 |
|
| 72 |
DÆVID |
| 73 |
|
| 74 |
-- |
| 75 |
gentoo-user@g.o mailing list |
Archives