lution
> Subject: Re: It's Time to Fix This Installation Stuff, Guys
>
>
> Kevin
>
> That is indeed awesome news. Should have known you guys would be ahead
> of me on this.
>
> Way to go.
>
> Dan
>
> On Sep 8, 2004, at 12:06 AM, Kevin Miller
Kevin
That is indeed awesome news. Should have known you guys would be ahead
of me on this.
Way to go.
Dan
On Sep 8, 2004, at 12:06 AM, Kevin Miller wrote:
On 8/9/04 1:15 am, "Dan Shafer" <[EMAIL PROTECTED]> wrote:
I realize RunRev has limited resources.
I realize that there are probably high
On 8/9/04 1:15 am, "Dan Shafer" <[EMAIL PROTECTED]> wrote:
> I realize RunRev has limited resources.
>
> I realize that there are probably higher priorities.
>
> But, really, guys, how hard would it be to finally fix the installation
> process so it was smooth? I am so tired of downloading a new
Andre Garzia wrote:
in the meantime, would it be hard for us to create a "migrator" stack
that would pick license.rev, the plugins and other important stuff and
merge with other Rev folder? I think we could do this, then if we
reinstall rev, press a button on the migrator stack, puf, cloned
ins
I agree. This moving and installing of new versions is extremely annoying. And it's
not hard to impliment some preferences somewhere on the system. What I've done is put
some preferences within the registry, or sometimes it goes in a preferences file in
the root folder.
But most importantly
What are you doing, Andre? Going for THREE apps in one day?
:-D
Dan
On Sep 7, 2004, at 5:38 PM, Andre Garzia wrote:
Dan,
in the meantime, would it be hard for us to create a "migrator" stack
that would pick license.rev, the plugins and other important stuff and
merge with other Rev folder? I thin
Dan,
in the meantime, would it be hard for us to create a "migrator" stack
that would pick license.rev, the plugins and other important stuff and
merge with other Rev folder? I think we could do this, then if we
reinstall rev, press a button on the migrator stack, puf, cloned
instalation... :D
> Isn't this really a matter of storing some of this information like
> prefs and license key in a folder that doesn't get
> overwritten by a new
> installation? How hard can that be?
>
> If I required my customers to go through these kinds of hoops every
> time I upgraded their software, they
