env: 1

[mpdehaan]

Hi Benno,

I notice a lot of roles are setting "RUNLEVEL: 1" in the environment variable (env) and passing it to the apt module when installing packages.

Can you let me know why this is? I don't see this in other roles and am thinking this may confuse people, or be otherwise something we should handle in the apt module?

Thanks!

[bennojoy]

Hi Micheal,

This is because apt would prompt for configurations options from the user for many packages. There are many ways to circumvent it so that user won't be prompted and the installation can be automated setting the environment run level to 1 is one of the ways.

• Benno

[mpdehaan]

Yeah, so anything like this where there is something prompting should be handled in the apt module already by the various flags we pass, so is a package misbehaving and those flags are not sufficient?

If you are finding something that is not respecting that option, let's figure it out, and only apply this on a case by case basis where the module is in fact prompting.

People are starting to copy this pattern for no reason and I don't want it to be a thing that people assume they have to do.

Let's patch the apt module to add this environment variable if we need to and only add this parameter for the packages that need it.

On Sun, Dec 22, 2013 at 10:02 PM, Benno Joy [email protected]:

Hi Micheal,

This is because apt would prompt for configurations options from the user for many packages. There are many ways to circumvent it so that user won't be prompted and the installation can be automated setting the environment run level to 1 is one of the ways.

• Benno

— Reply to this email directly or view it on GitHubhttps://github.com/bennojoy/network_interface/issues/3#issuecomment-31102488 .