Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.2.0 2018-05-11T15:58:46Z 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-04-12T07:59:47Z urn:sha1:6085ab7488326cfed8f82e07eefcbc2dc40d4bea Now that --with-source is supported in show we can go a little further and add the "syntactic sugar" of supporting deb-files on the commandline directly to give users an alternative to remembering dpkg -I for deb files & as a bonus apt also works on changes files. Most of the code churn is actually to deal with cases probably not too common in reality like mixing packages and deb-files on the commandline and getting the right order for these multiple records. Closes: 883206 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-01-26T22:33:25Z urn:sha1:ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49 The syntax is a bit awkward, but it is the same as for a package name and introducing another syntax wouldn't really help usability, so with apt install ./foo.deb/experimental you will get the dependencies of foo satisfied by your default release, but if this wouldn't satisfy the version requirements the candidate for this dependency is switched to the version from the experimental release. The same applies for apt build-dep ./foo.dsc/stable-backports which was the initial request. 2018-04-15T19:11:42Z Julian Andres Klode julian.klode@canonical.com 2018-04-13T10:32:35Z urn:sha1:e9796b9c21ee7d8e8f5d6e2a24db43fc4368b557 This allows third-party package managers like snap or flatpak to hook in and suggest alternatives if packages could not be found, for example. This is still highly experimental and the protocol might change in future versions. 2017-07-12T11:57:51Z Julian Andres Klode jak@debian.org 2017-07-12T11:40:41Z urn:sha1:87274d0f22e1dfd99b2e5200e2fe75c1b804eac3 This makes it easier to see which headers includes what. The changes were done by running git grep -l '#\s*include' \ | grep -E '.(cc|h)$' \ | xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/' To modify all include lines by adding a space, and then running ./git-clang-format.sh. 2017-07-12T11:56:05Z Julian Andres Klode jak@debian.org 2017-07-12T11:42:18Z urn:sha1:c46f94aa48a9707668c46118b3eec77ff318b78c Including cacheiterators.h before pkgcache.h fails because pkgcache.h depends on cacheiterators.h. 2016-07-22T14:05:09Z David Kalnischkies david@kalnischkies.de 2016-07-08T13:59:23Z urn:sha1:92296fe4b0862a04ea3d965b4cd2d4a420e3be9f We support installing ./foo.deb (and ./foo.dsc for source) for a while now, but it can be a bit clunky to work with those directly if you e.g. build packages locally in a 'central' build-area. The changes files also include hashsums and can be signed, so this can also be considered an enhancement in terms of security as a user "just" has to verify the signature on the changes file then rather than checking all deb files individually in these manual installation procedures. 2016-01-25T17:15:44Z David Kalnischkies david@kalnischkies.de 2016-01-21T22:22:00Z urn:sha1:a249b3e6fd798935a02b769149c9791a6fa6ef16 build-dep was implemented by parsing the build-dependencies of a package and figuring out which packages to install/remove based on this. That means that for the first level of dependencies build-dep was implementing its very own resolver with all the benefits (aka: bugs) this gives us for not using the existing resolver for all levels. Making this work involves generating a dummy binary package with fitting Depends and Conflicts and as we can't create them out of thin air the cache generation needs to be involved so we end up writing a Packages file which we want to parse – after we have parsed the other Packages files already. With .dsc/.deb files we could add them before we started parsing anything. With a bit of care we can avoid generating too much data we have to throw away again (as many parts assume that e.g. the count of packages doesn't change midair), so that on a speed front there shouldn't be much of a difference, but output can be slightly confusing as if we have a completely valid cache on disk the "Reading package lists... Done" is printed two times – but apt is pretty quick about it in that case. Closes: #137560, #444930, #489911, #583914, #728317, #812173 2015-11-29T16:00:11Z David Kalnischkies david@kalnischkies.de 2015-11-29T15:57:58Z urn:sha1:f6777222f82f6279c104138216b0e5e50d8caa67 Git-Dch: Ignore 2015-11-04T17:04:01Z David Kalnischkies david@kalnischkies.de 2015-10-12T13:57:53Z urn:sha1:14341a7ee1ca3dbcdcdbe10ad19b947ce23d972d The main part is refactoring through to allow hiding the magic needed to support .deb files in deeper layers of libapt so that frontends have less exposure to Debian specific classes like debDebPkgFileIndex. 2014-10-15T02:18:07Z David Kalnischkies david@kalnischkies.de 2014-10-15T02:18:07Z urn:sha1:9c81f8de38df940559d13a3ea9591d63cbe970bb We are checking the space requirements for ages, but the check uses the free blocks count, which includes the blocks reserved for usage by root. Now that we use an unprivileged user it has no access to these blocks anymore – and more importantly these blocks are a reserve, they shouldn't be used by apt without special encouragement by the user as it would be bad to have dpkg run out of diskspace and maintainerscripts like man-db skip certain actions if not enough space is available freely.