Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 389609 - Return 0 in emerge moo
Summary: Return 0 in emerge moo
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks: 381649
  Show dependency tree
 
Reported: 2011-11-05 11:24 UTC by Göktürk Yüksek
Modified: 2011-11-10 06:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
the output of git --diff (emerge-moo.patch,514 bytes, patch)
2011-11-05 11:25 UTC, Göktürk Yüksek
Details | Diff
the output of git --diff (emerge-moo.patch,544 bytes, patch)
2011-11-05 11:46 UTC, Göktürk Yüksek
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Göktürk Yüksek archtester gentoo-dev 2011-11-05 11:24:44 UTC
After typing "emerge moo", emerge successfully prints the expected output and then tries to resolve dependencies for "moo". If this is the only requested 'action', I think it's safe to return from that point (since there is no "moo" package in the tree and would be pointless to have this output if there is one). I attached a trivial patch also.

Reproducible: Always
Comment 1 Göktürk Yüksek archtester gentoo-dev 2011-11-05 11:25:53 UTC
Created attachment 291741 [details, diff]
the output of git --diff
Comment 2 Göktürk Yüksek archtester gentoo-dev 2011-11-05 11:46:50 UTC
Created attachment 291745 [details, diff]
the output of git --diff

Make it consider multiple "moo"s
Comment 3 Zac Medico gentoo-dev 2011-11-05 21:23:39 UTC
(In reply to comment #0)
> If this is the only requested
> 'action', I think it's safe to return from that point (since there is no "moo"
> package in the tree and would be pointless to have this output if there is
> one).

If we do that, I think we should make it emerge --moo, in order to avoid possible ambiguity. Meanwhile, we can keep the existing 'emerge moo' behavior exactly as it is, and show a deprecation message which suggests to use emerge --moo instead.
Comment 4 Göktürk Yüksek archtester gentoo-dev 2011-11-07 05:21:56 UTC
(In reply to comment #3)
> If we do that, I think we should make it emerge --moo, in order to avoid
> possible ambiguity. Meanwhile, we can keep the existing 'emerge moo' behavior
> exactly as it is, and show a deprecation message which suggests to use emerge
> --moo instead.

I think that's the way to go.
Comment 6 Göktürk Yüksek archtester gentoo-dev 2011-11-07 06:43:10 UTC
Should I close this bug then?
Comment 7 Zac Medico gentoo-dev 2011-11-07 07:39:04 UTC
Let's keep it open until it's released.
Comment 8 Zac Medico gentoo-dev 2011-11-10 06:11:26 UTC
This is fixed in 2.1.10.33 and 2.2.0_alpha73.