Bug#186767: apt: Release files should have a default pin-priority

[Carsten Hey <c.hey@web.de>]

Hi,

a default pin-priority as described in Goswin Brederlows mail would also
be very useful for backports.org.

Currently users have to configure pinning to get only the packages they
want.  When they make an error while configuring pinning (since pinning
is not that trivial this is very common for unexperienced users) they
will get _all_ backported packages.

Setting NotAutomatic to yes is not a solution, since users will miss
important security-updates for the backported packages they use.

So the only solution I see to provide sane defaults is to add something
like DefaultPriority and in case of backports.org set it to 101.  Client
side pinning should of course override the default priority provided by
the repository.

Backports.org is only an example where this would be useful, there are
many other repositories that would benefit from such a feature.

DefaultPriority could substitute NotAutomatic in Etch+1, since setting
NotAutomatic to yes is equivalent to setting DefaultPriority to 1.
Until NotAutomatic can been dropped, parsing NotAutomatic only when
DefaultPriority is not provided would imho be the right way. 


Regards
Carsten Hey