Jerome Haltom schrieb:
> Well, this has been discussed to death in various other places.
> On Thu, 2007-11-08 at 16:36 +0100, Tomasz Chmielewski wrote:
>> Jerome Haltom schrieb:
>>> Linux machines already have such technology. A few choices in fact. I
>>> use Apt.
>>> I configure my own Apt repositories, I upload packages I need to them. I
>>> make sure each host is configured to point at the proper apt repository,
>>> and use the distro's built in upgrade mechanisms.
>> That's for installing whole programs rather than running custom scripts.
> Tons of Deb packages distributed with the distribute itself run not much
> more than a script. I don't consider a .deb package necessarily as a
> piece of software, but more as a piece of functionality available to be
> added to a system. Some .deb files don't do anything more than form an
> abstract named entity (meta package).
>>> If I need advanced scripting, I just build my own .deb files. It's super
>>> easy and can be done with nothing more than a collection of text files.
>>> And versioning is handled automatically, dependencies, etc.
>> Building a .deb file to just run:
>> echo "foo bar" >> /etc/sudoers
>> Doesn't seem super easy and fast to me.
> Why not? It's great. You can manage the addition of this line as a
> "feature" to be installed on the OS as part of your standard
> installation procedure. Removing it then is just as easy as removing
> the .deb package.
Maybe you're right - after all, deb or rpm is just an underlying technology.
I can perfectly imagine a simple script, something ncurses based, or a
web-GUI to build a rpm/deb (or both) custom-advanced-script-only-package
(just ask a couple of questions, ask to point to a script or paste it,
Previously, I was looking for something which could ease the
administration of Linux stations, and I didn't find much.
cfengine comes to my mind, but it is unnecessarily complex.