On Wed, Aug 31, 2005 at 12:46:16AM -0600, Andreas Girardet wrote:
jigdo is OK for me, but I think just as bad for the average user than a script. The same user group that can handle a script can handle jigdo ....... If you cannot handle a script, then you won't be able to handle jigdo either. The command line level is the same, I assume.
That is not correct. A script will call various external tools, e.g. mkisofs, create_package_description, and so on. The user has to install all these tools to make it work. And do you have all these tools for all platforms the users might work on? The Windows jigdo package is self-contained and the Linux package only needs an installed wget. The user does not have to care about additional tools.
I must admit I have not seen jigdo on windows, but I assume it is a command line of some sort?
It is. But you could easily write a very simple Windows GUI application that pops up a dialog box that asks the required parameters and then calls the command line tool. If you do so the user does not have to call the command line tool himself.
If it is I doubt what you say, just since I did work for an ISP helpdesk many years ago and the sort of user you get there is the one we will be getting with Linux's continued success. Such a user is seriously overloaded with the concept of a command line all together. Burning an iso is mainly a wizard driven thing today and is click click done ..... not so jigdo or a script. Both are just as complex. Those users are the ones that do not use bittorrent and will be hammering our servers.
Correct me if I am making wrong assumptions in my conclusions.
No, I think you are correct here but as I said it is not that much effort to write a simple GUI wrapper for those users. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de