| Summary: | emerge --help doesn't document "S" flag in emerge --pretend output | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Andrew Cowie <andrew> |
| Component: | Documentation | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | Keywords: | InVCS |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Andrew Cowie
2004-10-27 23:23:30 UTC
Any objections against trimming the emerge --help output to show only the basics? No point in duplicating the information contained in the man page... You know, I was actually wondering about that. For what it's worth, the basics would be fine. Ie, `emerge --help` would say something like what emerge (bare, no options) says plus a nice comment describing taht `man emerge` is really what someone wants to do to get help. It would probably also be good to note that it is really important to run `emerge --pretend blah` before `emerge blah` (just to help the newbies). Over to you AfC Toronto Documented the "S" in the output as well as fixing up a few other missing/incorrect parts. Will look at sorting out the duplication later. Question: So this is really a "note to developer, please do what you will with it" type bug; is there a policy reason that, now that you've made a change, you can't just close this? I've been looking around, and I get the sense that a lot of people who report bugs don't realize that they're supposed to loop back and close them. My sense is that since you think you've dealt with it, you should mark it FIXED; if I had a problem with what you did by the time it made it into a future portage version (many months later) me doing a REOPEN would be more appropriate [I'm soon to be a dev in the Java herd, so I thought I should ask how this sort of thing is "supposed" to be handled] AfC Well, the fix is not in .51-r3 as far as I can see and we usually keep the bugs open until the fix is released, that's what we (= dev-portage) use the InCVS keyword for, other teams might use different rules. Well, it's fixed in 2.0.51.19 (and probably was a long time ago). Closing. AfC Toronto |
