|
Bugzilla – Full Text Bug Listing |
| Summary: | make -q really quiet (don't display progress) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Ian Marlier <ian.marlier> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED FIXED | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | stephen |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ian Marlier
2008-02-06 13:34:19 UTC
this is a dup of a bug I don't remember :) It is related to bug 336333, but not a duplicate. (In reply to comment #0 from Ian Marlier) > It appears that this behavior does not change when zypper is given command line > options such as -q (quiet) or -n (non-interactive). > > It would be very nice to have a flag that would suppress the output of the > progress meter. The -q options is meant to be really quiet, so that is what you want after it gets fixed. > (Note: I'm not sure about the license/etc for zypper, but assuming that it's > open I'd be happy to take a stab at implementing this.) It's GPL, you're welcome to participate :O) We already have a plan to deal with zypper's output, which, after implemented, will deal also with this bug. The main idea is to add --xml option to switch zypper to a well defined xml output. This will need a major change in the way the output is written throughout the code and we'll keep bugs like this in mind doing it. Currently i'm trying to design classes and functions which will be used for output. The fix for this -q vs. progress output bug is probably easy, but i decided not to do it until the above is done (which i hope will be soon (this month)). btw: see http://en.opensuse.org/Zypper/Development *** Bug 343671 has been marked as a duplicate of this bug. *** --xmlout almost done, and this bug fixed already. In svn. To be in zypper 0.10.1 submitted |