Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This follows recent changes in apt which added support for
files greater than several gigabytes in size -- using the
'unsigned long long' type to store the file size.
Changelog download is restored as a result of this.
Closes: #669569
LP: #824708
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also added ?term-prefix to the test suite (oops).
|
|
|
|
* Verify that ~ parses as a name matcher, not a term matcher.
* Verify that a top-level bare string that's not ~ parses as a name matcher.
|
|
These never worked out as well as I intended, and all indications
were that they would be a maintenance burden...or just bitrot.
Fully parallel builds are nice, but my builds are pretty quick on
my 8-core box even with the artificial chokepoints that automake
induces.
|
|
SizeToStr() now outputs a space between its nubmer and its units.
Arguably this is a case of tests that are too fragile: I should be able
to cut that dependency with a mock and thus avoid being broken by changes
to how SizeToStr() behaves.
|
|
Whoever's in charge of libapt these days apparently doesn't believe in
backwards compatibility. Or in documenting how their APIs are to be
used, or why names are deprecated </gripe>
|
|
Setting a category to OFF was supposed to mean that nothing in that category
was logged. Instead, it logs everything, and logging a message at OFF disables
it (which is ... sort of useless).
Fixed the behavior, and the tests, to behave correctly. Setting a log category's
level to OFF suppresses all its messages now.
|
|
|
|
Also documented this new behavior and wrote a unit test for it.
|
|
we're using a strict mock now.
Not only is it unnecessary, it was generating confusing error messages if
newline() was expected but occurred out of order.
|
|
It's really just a hack to break the command-line implementation up in a
way that's more amenable to unit-testing; it doesn't belong in the generic
view interface.
|
|
because it's already downloaded.
|
|
|
|
the whole download process is complete.
Necessary to fully expose the events generated by
download_signal_log.
|
|
|
|
|
|
|
|
I can't use Mock directly because this class already inherits
from Mock, so there would be confusion about which static
members to expose (well, I could resolve it, but that's
about as much trouble as implementing the interface directly).
|
|
|
|
everywhere.
|
|
the tests.
|
|
piece of its functionality.
This will make some of the tests easier to write, since often some of
the code requires just the ability to read the screen width, or just the
ability to read input from the terminal. Splitting the terminal interface
means no need to mock out the parts that aren't used.
|
|
As a side effect, this creates a "controllers" directory in the generic tree,
and removes the now-empty GTK+-specific controller and view directories.
The README files are moved over to the generic locations and tweaked to be
correct for their new home.
|
|
|
|
|
|
|
|
Its only real purpose was to do what display_and_advance() does better --
i.e., display a durable progress notification and move to the next line.
|
|
|
|
to the next line.
This should be useful for things like printing a status message alongside
some sort of progress indicator -- set_text() followed by advance() is not
really ideal since it truncates the line.
|
|
implementation for showing the download progress at the command line and a stub implementation.
This is mostly just a streamlining of the apt interface, but putting the
code behind a clean view will also make it much more testable.
|
|
isn't being built.
|
|
If the GTK+ frontend isn't built, neither is the controller,
so the test won't build.
|
|
include file, but I prefer listing all the dependencies anyway.
|
|
separate file to reduce test dependencies.
No reason for tests to pull in half of src/generic/apt just because a module
linked into the test happens to reference a global pointer.
|
|
It looks like I disabled two of them to speed up testing, then accidentally
committed that change.
|
|
current task is done, and for displaying progress the way classic apt tools do.
The new code supports both "[ 40%] Task" and "Task... 40%" display styles,
and when a task is complete the code will either erase it (default) or advance
to the next terminal line (like apt-get does). These behaviors are controlled
by apt options.
|
|
Instead of relying on knowing how many times each routine checks for throttling,
I just fully disable and fully enable throttling depending on whether the next
call should be throttled or not.
|
|
InSequence().
Note that calls to get_screen_width() are left off, since we don't care when
it happens and it can happen any number of times.
|
|
advancing to the next line.
i.e., for explicitly outputting a newline. The main advantage of this is
that it lets me give the progress display a mode that emulates the old apt
progress display (specifically, the behavior that completed steps remain
visible).
|
|
actually changed.
In particular, this means that outputting "\n" after a flush won't
redundantly update the last line.
|
|
isn't a terminal.
|