Re: sources.list best practices

[Brad Alexander <storm16@gmail.com>]

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 not the release name (stable, testing, unstable) to protect against inadvertent upgrades.

I'm still torn between a single monolithic sources.list and putting a bunch of small files in sources.list.d. I am actually leaning toward the former. Puppet will fairly easily allow me to maintain multiple directories with the base sources.list, and facter, a component of puppet, actually has a variable for operatingsystemrelease:

# facter operatingsystemrelease
6.0.3

# facter operatingsystemrelease
wheezy/sid

So I'm thinking of having a pristine sources.list in /etc/apt, and the extra lists in sources.d. I will then separate by stable vs. testing/unstable...

Any other ideas?

Thanks,
--b

On Wed, Nov 16, 2011 at 3:58 AM, Andrei Popescu <andreimpopescu@gmail.com> wrote:

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 squeeze)
$ ls -1 /etc/apt/sources.list.d/
marillat.list
skype.list
squeeze-backports.list
squeeze.list
squeeze-security.list
squeeze-updates.list

(sid)
$ ls -1 /etc/apt/sources.list.d/
experimental.list
lenny.list
marillat.list
skype.list
squeeze.list
wheezy.list

but I would go with the method that fits puppet better.

Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic