Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.2.2 2015-12-11T13:48:21Z 2015-12-11T13:48:21Z Julian Andres Klode jak@debian.org 2015-12-11T13:27:56Z urn:sha1:fffa3b57b4f2334dff3b9bef5401521307e1a721 dpkg does that when reading package files, so we should do the same. This only deals with parsing names from binary package paragraphs, it does not look at source package names and/or the list of binaries in a dsc file. Closes: #807012 2015-08-10T15:25:25Z David Kalnischkies david@kalnischkies.de 2015-06-18T15:33:15Z urn:sha1:3d8232bf97ce11818fb07813a71136484ea1a44a Various small leaks here and there. Nothing particularily big, but still good to fix. Found by the sanitizers while running our testcases. Reported-By: gcc -fsanitize Git-Dch: Ignore 2015-08-10T15:25:25Z David Kalnischkies david@kalnischkies.de 2015-06-17T07:29:00Z urn:sha1:6c55f07a5fa3612a5d59c61a17da5fe640eadc8b Doing this disables the implicit copy assignment operator (among others) which would cause hovac if used on the classes as it would just copy the pointer, not the data the d-pointer points to. For most of the classes we don't need a copy assignment operator anyway and in many classes it was broken before as many contain a pointer of some sort. Only for our Cacheset Container interfaces we define an explicit copy assignment operator which could later be implemented to copy the data from one d-pointer to the other if we need it. Git-Dch: Ignore 2015-06-16T14:22:46Z David Kalnischkies david@kalnischkies.de 2015-06-16T14:22:46Z urn:sha1:c8a4ce6cbed57ae108dc955d4a850f9b129a0693 To have a chance to keep the ABI for a while we need all three to team up. One of them missing and we might loose, so ensuring that they are available is a very tedious but needed task once in a while. Git-Dch: Ignore 2015-03-16T17:01:13Z David Kalnischkies david@kalnischkies.de 2015-01-08T20:07:37Z urn:sha1:2f6a2fbbdc9f76dc4eace83a427013f4e1c03afc Implementing FileName() works for most cases for us, but other frontends might need more and even for us its not very stable as the normal Jump() implementation is pretty bad on a deb file and produce errors on its own at times. So, replacing this makeshift with a complete implementation by mostly just shuffling code around. 2014-10-13T11:01:15Z David Kalnischkies david@kalnischkies.de 2014-10-13T07:54:21Z urn:sha1:9d653a6de2ca952247cc4e628256259d225570a6 I am pretty sure I did that before committing broken stuff… Git-Dch: Ignore 2014-10-13T09:29:39Z David Kalnischkies david@kalnischkies.de 2014-10-13T06:05:57Z urn:sha1:862bafea48af2ceaf96345db237b461307a021f6 Reimplementing an inline method is opening a can of worms we don't want to open if we ever want to us a d-pointer in those classes, so we do the only thing which can save us from hell: move the destructors into the cc sources and we are good. Technically not an ABI break as the methods inline or not do the same (nothing), so a program compiled against the old version still works with the new version (beside that this version is still in experimental, so nothing really has been build against this library anyway). Git-Dch: Ignore 2014-05-09T11:06:27Z David Kalnischkies kalnischkies@gmail.com 2013-08-18T20:20:25Z urn:sha1:ffe3c68e494efc1c2c4d748fa9d69e150867e5c2 It seems unlikely for now that proper archives will carry multiple Description-* stanzas in the Packages (or Translation-*) file, but sometimes apt eats its own output as shown by the usage of the CD team and it would be interesting to let apt output multiple translations e.g. in 'apt-cache show'. 2014-05-09T11:06:27Z David Kalnischkies kalnischkies@gmail.com 2013-08-18T22:00:23Z urn:sha1:b3501edb7091ca3aa6c2d6d96dc667b8161dd2b9 It is not very extensible to have the supported Hashes hardcoded everywhere and especially if it is part of virtual method names. It is also possible that a method does not support the 'best' hash (yet), so we might end up not being able to verify a file even though we have a common subset of supported hashes. And those are just two of the cases in which it is handy to have a more dynamic selection. The downside is that this is a MAJOR API break, but the HashStringList has a string constructor for compatibility, so with a bit of luck the few frontends playing with the acquire system directly are okay. 2014-03-13T12:58:45Z David Kalnischkies david@kalnischkies.de 2014-03-05T21:11:25Z urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f Beside being a bit cleaner it hopefully also resolves oddball problems I have with high levels of parallel jobs. Git-Dch: Ignore Reported-By: iwyu (include-what-you-use)