Bug#596097: apt: Please support setting a pin of 100 from within an archive (NotAutomaticButUpdates)
* Julian Andres Klode <email@example.com> [2010-09-08 18:58:05 CEST]:
> On Mi, 2010-09-08 at 18:31 +0200, Alexander Wirt wrote:
> > It would be great if apt would support a Flag like:
> > NotAutomaticButUpdates or so which pins a remote repo to 100. If
> > needed I can provide a patch but my C++ isn't so fluid, so I would
> > prefer if I don't have to :).
> > For backward compability it would be nice NotAutomatic and
> > NotAutomaticButUpdates would both work.
> > Also it would be great if we could get the change into Squeeze :).
> My opinion: It may break some applications making use of NotAutomatic
> flags if you suddenly add a third type of sources (0, NotAutomatic,
> NotAutomaticButUpdates). But the breakage is probably not that hard.
> I'd like to have per-source default pin priorities instead of yet
> another NotAutomatic flag, but that's too complicated and breaks the
Sounds like a "DefaultPriority: 100" entry in the Release file might be
what you are suggesting? If that's the case that sounds pretty flexible
but please make sure that it overrides the NotAutomatic entry so that
for backward compatibility the Release file can have both.
Thanks for the brainstorming!