Josh Soref wrote:
>
> Josh Soref wrote:
> > Mozilla nightly binaries are not necessarily binary compatible w/ previous
>nightlies.
>
> > I think, if you always delete component.reg, *.xpt, *.dll, and *.exe from your
>mozilla install directory you should not have this problem.
>
> JTK wrote:
> > Shouldn't the installer take care of that?
>
> Um, exactly what should the installer do (and how)?
Just what you said: always delete (or overwrite with the new versions)
component.reg, *.xpt, *.dll, and *.exe from your mozilla install
directory, and these things shall cease to happen amongst us. Isn't
that what you're saying?
> Right now, the installer can't know if you have compatible or incompatible
>libraries lying around.
Nor should it care. Overwrite them, the ones it itself installed last
time, and we're done.
> Nor can it know if you have outdated libraries that should be trashed. We could
>teach it a list of such libraries, but eventually installer would be 90%+ of the
>mozilla distribution -- not a good idea.
>
No, come on.
> Installer's do say something like ~don't install me over an existing install~ and
>perhaps ~may i nuke your existing install~. [note this is binaries, not profile data
>-- although we also don't assert profile compatibility]
So you're trying to tell me that the installer "can't" overwrite
binaries and scripts that it installed the day before?
