Gossamer Forum
Home : Products : Gossamer Links : Discussions :

Automatic install vs classic

Quote Reply
Automatic install vs classic
Hi all,
i have tested 2.0 the last hours and found out the following out for me:
It ist shurely a nice thing especially for newbies to have an automatic routine to install links,
but i would prefer really a clean install for myself with only files to ftp.
Cause i will change in future every single file as i do that in the past, i will compare new and old files in my ascii-editor and change only what i need. With the automatic i must do first a clean install on the server than get the files back, compare, change and put it back.
So is there a way to get the files without that?
What do you think about?

Robert

Quote Reply
Re: Automatic install vs classic In reply to
Hello Robert!

I was just going to post a message and saw that someone had the same problems. in the installation it needs to ask to simply unpack or install. I tried to do it with the browser and ran in to problems as it was installed with the user nobody on a shared server. No chance to erase it.

I would prefer also a basic unpack option.

By the way, *.pm needs to be uploaded in ASCII or binary format?

Quote Reply
Re: Automatic install vs classic In reply to
Hi Robert,

The install.dat file is simply a tar file. You can rename it to install.tar and unarchive it using Winzip or something else.

As for permissions, you should run the script from shell/telnet to have it installed as your own user.

Cheers,

Alex

--
Gossamer Threads Inc.
Quote Reply
Re: Automatic install vs classic In reply to
.pm are perl-files, too. īThe only difference is, that you will use them as includes not as files to call.
So 644 instead 755.

;-)
Robert