Julien BLACHE <jblache@debian.org> writes:
> Arnaud Vandyck <avdyk@debian.org> wrote:
>
> Hi,
>
> Well, I was waiting for someone to ask that very question...
>
>> What is the difference between your tool and do a
>>
>> $ dpkg --get-selections > list-of-master-packages.txt
>> $ scp list-of-master-packages.txt user@host:/root/slave-packages.txt
>> $ ssh host -l root
>> # dpkg --set-selections < slave-packages.txt
>> # aptitude install
>
> The answer is quite simple : it's all automated. Ok you could write a
> script that does just that, it'll take a couple of minutes to
> write. Sure.
Sure.
> The interest of debsync, IMHO, does not really reside in what it can
> do *now* but rather in what it will be able to do in the future (like
> processing the remote hosts in parallel rather than one after the
> other).
OK, let's add a 'for' statement with a list of hosts! ;)
> From what the author told me, there should be a couple of improvements
> in the next version, even if it'll probably still be an equivalent to
> your 5 commands above. (btw, I'd like to see you use your 5 commands
> to update, say, a hundred remote hosts. I'd offer the coffee)
I don't understand. If I make a script (with a loop!;)), why can't I put
it in a cronjob? Also, note that the --set-selections needs to be done
once (or everytime you add/remove a package on the master host), all the
other times it's only an update.
> In my experience, the use of dpkg --{get,set}-selections is something
> that is not widely known, and still a very manual thing. What I see in
> debsync is a tool that will come with the distro, ready to use, and
> that won't require a "deep" knowledge of the interactions between apt,
> dpkg and dselect.
dpkg comes with the distro and man or --help show the
--{get/set}-selections. Also, it's in the beginner gide or another doc I
don't remember which ;)
> What's important here is *having* the _tool_. The fact that it does
> what you could do in 5 commands is irrelevant. And if you were to
> write the script yourself, you'd have to test/debug it, etc.
I don't agree.
1° We already have the tools (dpkg, ssh, aptitude)
2° If every scripts have to be package, I think we'll have some problems
in the distro! Also, note that ssh and aptitude are tools that must
be known by the average administrator (and I think your tool is for
admins, not users who don't have the right to install anything). And
if this admin read some docs about Debian, he'll learn dpkg fast!
3° Well, yes, you'll have to test!
> I hope you see my point now :)
I think, but do you see mine?
Cheers,
--
.''`.
: :' :rnaud
`. `'
`-
Attachment:
pgpcqSTir9EZq.pgp
Description: PGP signature