On Tue, 16 May 2006 15:09:37 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
How so? As an admin you can always comment out any conf.d file completely
if you don't want what is in there. After which dpkg will come with the
usual prompt at package upgrade about the conf-file being
Marc Haber [EMAIL PROTECTED] writes:
On Tue, 16 May 2006 15:09:37 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
How so? As an admin you can always comment out any conf.d file completely
if you don't want what is in there. After which dpkg will come with the
usual prompt at package
On Wednesday 17 May 2006 08:33, Marc Haber wrote:
On Tue, 16 May 2006 15:09:37 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
How so? As an admin you can always comment out any conf.d file
completely if you don't want what is in there. After which dpkg will
come with the usual
On Wed, 17 May 2006 12:33:21 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
= /etc/something.d directory might not be perfect, but it's good sight
better then monolitic configuration files
Agreement on that.
Greetings
Marc
--
-- !! No courtesy
On Mon, May 15, 2006 at 10:47:48AM +0200, [EMAIL PROTECTED] wrote:
Am 15.05.2006 um 10:32 Uhr haben Sie geschrieben:
CFEngine is in Debian, but has some real nasty frustrations. Puppet
isn't in Debian, but Jamie is working hard on the packages and I've got
some provisional ones built from
On Monday 15 May 2006 09:49, [EMAIL PROTECTED] wrote:
Hi,
in case I am in the wrong list, I beg you pardon, but I asked this
already in debian-user without success.
I would like to build customized, configured packages (for example
additional bash script for the bash package, some default
On Tue, 16 May 2006 10:28:57 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
1) use multilevel/modular config where available:
usually in the form of a /etcc/something.d directory
(e.g. /etc/apt/conf.d), or stacked config sets (e.g. the major desktop
environments, see
On Tuesday 16 May 2006 12:10, Marc Haber wrote:
On Tue, 16 May 2006 10:28:57 +0200, cobaco (aka Bart Cornelis)
[EMAIL PROTECTED] wrote:
1) use multilevel/modular config where available:
usually in the form of a /etcc/something.d directory
(e.g. /etc/apt/conf.d), or stacked config sets
Hi,
in case I am in the wrong list, I beg you pardon, but I asked this
already in debian-user without success.
I would like to build customized, configured packages (for example
additional bash script for the bash package, some default keybindings
for screen, some host in /etc/ssh/known_hosts
On Mon, May 15, 2006 at 09:49:00AM +0200, [EMAIL PROTECTED] wrote:
in case I am in the wrong list, I beg you pardon, but I asked this
already in debian-user without success.
Custom *packages* is probably more on-topic for debian-mentors, but I don't
think that custom packages are the right
Am 15.05.2006 um 10:32 Uhr haben Sie geschrieben:
On Mon, May 15, 2006 at 09:49:00AM +0200, [EMAIL PROTECTED]
wrote:
[...snip...]
Custom *packages* is probably more on-topic for debian-mentors, but I
don't
think that custom packages are the right solution.
Sorry for that.
What would be
11 matches
Mail list logo