Re: Best practices for development workstations
On Wed, Mar 31, 2010 at 02:44:48PM +0800, Paul Wise wrote:
> > I'm having a bit of trouble visualizing how that works; can you spell
> > out your apt settings?
>
> Something like this (not my exact settings):
>
> Package: *
> Pin: release a=stable
> Pin-Priority: 700
>
> Package: *
> Pin: release a=testing
> Pin-Priority: 650
>
> Package: *
> Pin: release a=unstable
> Pin-Priority: 600
>
> Package: *
> Pin: release a=experimental
> Pin-Priority: 550
>
> The priorities need to be > 500 and < 1000.
==> /etc/apt/preferences.d/experimental <==
Package: *
Pin: release a=experimental
Pin-Priority: 50
==> /etc/apt/preferences.d/testing <==
Package: *
Pin: release a=testing
Pin-Priority: 800
==> /etc/apt/preferences.d/unstable <==
Package: *
Pin: release a=unstable
Pin-Priority: 700
==> /etc/apt/preferences.d/stable <==
Package: *
Pin: release a=stable
Pin-Priority: 500
(actually I do not have the last one: 500 is the value given to
non-specified versions). If you have a default release, it is given
990 without any other intervention.
What you should care for is giving priorities between 101 and 989 to
non-default release. I use a script called apt-origins to check where
my packages come from (for example, I only have unison-2.13.16 and xpdf
installed from stable).
I prefer to always rate stable lower than testing, because a package
that is no more in testing but is in stable is suspicious at best (it
was removed from testing at some point).
And for the rest of the thread, I use pbuilder chroots. Testing of
non-controversial packages goes on either my home box (unstable/testing,
arch=amd64) or my lab box (testing/unstable, arch=amd64 kernel+i386
userland) or my laptop (testing/unstable, arch=i386). The more complicated
things I have a kvm virtual machine for, except for drivers and such.
Sincerly
--
Jean-Christophe Dubacq
Reply to: