Re: sources.list best practices

2011-11-16 Thread Andrei Popescu
On Ma, 15 nov 11, 17:58:16, Brad Alexander wrote: The third option is to dispense with a sources.list altogether, and put release-specific .list files in sources.list.d. Of course, you could have permutations of the above. Did I miss any options? This is what I do now on all machines: (pure

Re: sources.list best practices

2011-11-16 Thread Brad Alexander
Actually, Andrei, that will fit puppet well. I was just looking for methodologies, and I think that you and Tong pointed out a couple of important points. First, never cross the streams on stable. I'm guessing here that both of you probably use the codename (e.g. squeeze, lenny, wheezy, etc) and

Re: sources.list best practices

2011-11-16 Thread Arno Schuring
Brad Alexander (stor...@gmail.com on 2011-11-16 10:07 -0500): Actually, Andrei, that will fit puppet well. I was just looking for methodologies, and I think that you and Tong pointed out a couple of important points. First, never cross the streams on stable. I'm guessing here that both of you

sources.list best practices

2011-11-15 Thread Brad Alexander
Hey all, I've been doing the same thing the same way, but I would be interested to hear what others are doing and the pros and cons of the various approaches. Traditionally, I have replaced /etc/apt/sources.list with a universal one that includes stanzas for stable, testing, unstable, and in