Alec S. wrote:
> On Mar 17, 1:19 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
>> Alec S. wrote:
>>> On Mar 17, 12:07 pm, Alf Christophersen
>>> <alf.christopher..._at_medisin.uio.no> wrote:
>>>> And what do you do when uninstalling the application by removing just the folder and leave the registry full of crap?
>>> regedit /s uninstall.reg
>> Great! You just broke every application that requires *one* (or more)
>> components of the application you just uninstalled.
> You seem to know a lot about what apps I have and am talking about
> even though you <i>shouldn't</i> have any reason to. How exactly do
> you know? Is there some kind of program or website you use, are you
> viewing some kind of spyware on my system, or are you just psychic?
With "regedit /s uninstall.reg" you remove all the registry entries the
application needed when you installed it. Including all the entries for
By removing those, you broke all other applications which require those
shared objects, because you removed the registry entries for those too.
I'm not psychic, I just hate it when people think they can use their own
way to do things without considering other applications at all. There
are just too many devs and people like you out there who think their way
is ok just because 'it worked before'. Do you know how many times I had
to deal with broken applications which I had nothing to do with but
which broke TSVN? Just search the mailing list!
I don't care if you break your own system that way. But if you then come
here complaining about TSVN making it hard for you...
>>> I don't like installer in general; I didn't complain about MSI
>>> specifically, but now that you mention it, MSIs get copied into the
>>> \Windows\Installer for starters.
>> Only a part gets copied there, and that part is required for "repair application".
> And even that is a waste of space. How many times do you need to
> repair an application? Isn't it sufficient to use the original
> installation media on those rare occasion? I have seen that folder
> explode into the gigabyte range because even though as you said it
> only needs the parts to repair, that often ends up being pretty much
> the whole thing, so that a single package is 10-50MB.
In case you don't know: there's a registry setting where you can
deactivate that behavior of the Windows installer. But once you activate
it, you have to insert the installation CD/DVD for every update or
change you make.
>>>> Why would someone want to do all the registering manually? That's like
>>>> copying a picture by drawing it again instead of using a copy machine.
>>> Control, security. Try getting the government (or even corporations)
>>> to use software that they cannot trace and control every component of.
>>> That's why Easter Eggs have been banned in all government software.
>> That's why there's open-source, where you can trace *everything* (try
>> that with a commercial application).
> And oddly enough, governments and corporations are exactly the ones
> who still resist open source. Just last week I read an article in a
> trade paper about how banks are at the top of the list of OSS
Now guess who's paying them to do that :)
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-03-17 20:40:05 CET