apt - Debians commandline package manager

	Commit message (Collapse)	Author	Age	Files	Lines
*	srvrec: Do not expose C++11 tuple use in header	Julian Andres Klode	2015-10-30	1	-0/+7
\| \| \| \|	This makes non-C++11 reverse deps wishing to use it FTBFS.
*	GetSrvRecords: Make thread-safe	Julian Andres Klode	2015-10-30	1	-2/+7
\| \| \| \|	Gbp-Dch: ignore
*	avoid triggering the c++11 erase api change on travis	David Kalnischkies	2015-09-02	1	-2/+2
\| \| \| \|	Git-Dch: Ignore
*	use clock() as source for SRV randomness	David Kalnischkies	2015-09-01	1	-22/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Initializing a random number generator with the time since epoch could be good enough, but reaches its limits in test code as the 100 iterations might very well happen in the same second and hence the seed number is always the same… clock() has a way lower resolution so it changes more often and not unimportant: If many users start the update at the same time it isn't to unlikely the SRV record will be ordered in the same second choosing the same for them all, but it seems less likely that the exact same clock() time has passed for them. And if I have to touch this, lets change a few other things as well to make me and/or compilers a bit happier (clang complained about the usage of a GNU extension in the testcase for example).
*	Add basic (non weight adjusted) shuffling for SrvRecords selection	Michael Vogt	2015-08-20	1	-3/+56
\| \| \| \| \|	Also add "Debug::Acquire::SrvRecs" debug option and the option "Acquire::EnableSrvRecods" to allow disabling this lookup.
*	apt-pkg/contrib/srvrec.cc: res_query() should not generate a _error->Warning()	Michael Vogt	2015-08-18	1	-0/+2
\|
*	cleanup	Michael Vogt	2015-08-18	1	-5/+5
\|
*	WIP start randomizing	Michael Vogt	2014-05-23	1	-2/+29
\|
*	WIP make connect use GetSrvRecords	Michael Vogt	2014-05-22	1	-0/+14
\|
*	add sorting by priority	Michael Vogt	2014-05-20	1	-0/+7
\|
*	add GetSrvRecord helper to apt-pkg/contrib/srvrec.{cc,h}	Michael Vogt	2014-05-20	1	-0/+93