Re: Install question

"Mark Chaney" <[email protected]> Tue, 10 Sep 2002 06:32:35 -0400 (EDT)
Newsgroups gmane.comp.web.envolution.devel
Message-ID <[email protected]>
How about only including 2 or 3 themes then or maybe just one and having
the other ones as an option and a seperate download. Going through the
different directories and chmoding all of them is about 6 times more work
than a normal install. Im not saying that its hard, im just saying that its
unneeded work. Especially when u consider that X-Industries, Liquid Logic,
and LogicII are basically the same theme if u ask me. Also, like i covered
in my notes for ideas for Envolution, it would be a good idea to have
seperate packages. Minimal, Standard, and Full. These notes were written
over a month ago, but if you havent checked them out, you can see them here:
http://www.macscr.com/envolution.htm

Im not trying to be picky or difficult. Im just trying to make things more
userfriendly and give a better first impression to users installing
Envolution.

-MACscr

> On Tue, 2002-09-10 at 04:53, Mark Chaney wrote:
>> If i remember right, I have to install all themes with the install.
>> And if i try and just remove the theme before install, i will get an
>> error, right?
>
> Remove it after install!
>
>> The reason is, is that for people like me, i only want one them. The
>> original, and then i will hack the heck out of it. =P Or maybe i dont
>> want a theme at all and i just want mine. Because I hate having to go
>> chmod a bunch of directories to themes I wont use.
>
> Another approach would be to simply delete the skins you no longer
> require after install.
>
> It would be nice to have the option at install to select which
> themes/skins get installed if any....but where do you draw the line in
> the sense of how you package the release.
>
> For example I may not want the AvantGo module...yet many do...so isn't
> it much simpler to delete what you don't need after install.
>
> What I'm getting at is that packaging the installer to cover every
> possible combination of themes/skin/modules/features etc would
> definitely be a nice feature ... but is the work required to design
> implement and test such a feature worth the effort considering they can
> simply be deleted after installation as desired by the end user???
>
> Not a flame...just another perspective.
>
>>
>> Just wondering, i know there is a new installer for themes and maybe
>> this will be addressed. Just wanted to bring it up. =P
>>
>> BTW, isnt it possible to tar up a file with the correct permissions?
>> Does that effect file ownership too? If so, couldnt we just tar the
>> files with the correct permissions already set to the config.php files
>> and the cache folders? I know this would only affect people using unix
>> and uncompressing the file on the server, but i think this would
>> definately be a nice option.
>
> I agree with you here 100%.
>
> File ownership isn't affected, but permissions may very well be.
>
> And honestly this is my fault since I created the tarballs. I didn't
> consider users who uncompress on the server itself. I'll make sure to
> package future tarballs with perms intact. Good observation!!!!!!
>
>
> Zoom
>
>
>
>
> _______________________________________________
> Envdev mailing list
> [email protected]
> http://www.madhatt.info/mailman/listinfo/envdev_madhatt.info