apt/apt-pkg/sourcelist.cc, branch 1.3_rc2

don't count each Type as an individual deb822-sources stanza

2016-08-17T18:35:47Z

Reported-By: Mattia Rizzolo in #834629

add --with-source option and Packages/Sources support

2016-08-17T12:12:25Z

We support "./foobar.deb" as a way to install a deb file directly. Recently .changes files were added. This highlights a problem as you can't add the changes file without also trying to install all of them. Now, it could also be handy to add entire Packages/Sources files to perhaps get a bunch of packages in without installing them all implicitly. This commit introduces --with-source which allows to add *.deb, *.changes, *.dsc, source-dirs, Packages & Sources files (the later can also be compressed) without also installing them.

support "install ./foo.changes"

2016-07-22T14:05:09Z

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.

if conf unset, don't read / as conf/pref/sources dir

2016-06-29T10:22:33Z

Usually these config options are set to sensible values, but if init isn't run or the user interferes with configuration clearing or similar the options could indeed carry an empty value, which will result in FindDir returning a '/'. That feels kinda wrong, but as a public interface there isn't much we can do about it and instead make it so that we get the special file /dev/null back we know how to deal with in such cases.

deb822: Restore support for -{Add,Remove}

2016-04-28T08:08:32Z

Redesign of multivalue options in 463c8d801595ce5ac94d7c032264820be7434232 caused the parser to look for {Add,Remove} (no hyphen) instead of the expected -{Add,Remove}.

properly parse comments in apt_preferences and deb822-style sources

2016-01-02T15:20:01Z

apt_preferences and deb822-style sources used the specialized class pkgUserTagSection to deal with comments before/after a given stanza, but it couldn't deal with comments in the stanza at all. codesearch suggests that nobody else does and a vastely superior way of working with potentially commented files is implemented now, so we can officially discourage the use of the old incomplete hack class.

require explicit paths to dsc/control as we do for deb files

2015-12-01T13:26:05Z

Otherwise a user is subject to unexpected content-injection depending on which directory she happens to start apt in. This also cleans up the code requiring less implementation details in build-dep which is always good. Technically, this is an ABI break as we override virtual methods, but that they weren't overridden was a mistake resulting in pure classes, which shouldn't be pure, so they were unusable – and as they are new in 1.1 nobody is using them yet (and hopefully ever as they are borderline implementation details). Closes: 806693

accept ../ on the cmdline as start for a deb file as well

2015-11-29T13:32:29Z

Regression of 14341a7ee1ca3dbcdcdbe10ad19b947ce23d972d. Reported-By: Julian Andres Klode

support .deb files in upgrade operations as well

2015-11-04T17:04:01Z

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.

add by-hash sources.list option and document all of by-hash

2015-09-14T13:22:19Z

This changes the semantics of the option (which is renamed too) to be a yes/no value with the special additional value "force" as this allows by-hash to be disabled even if the repository indicates it would be supported and is more in line with our other yes/no options like pdiff which disable themselves if no support can be detected. The feature wasn't documented so far and hasn't reached a (un)stable release yet, so changing it without trying too hard to keep compatibility seems okay.