I'm sorry if I offended you that wasn't my intention. Don't tell me I'm not
thinking.

1. Do you know what gems are and how they work? It's like the GAC
2. It's easy to find out the location of a certain file from script and go
from there (killing the need for the PATH variable)
3. exactly it's about a repeatable and scriptable process. so I don't think
an installer will do the trick you know, but invoking an included script
does.
4. I fully realise what a build server is, how you do automated deployments
and how you provision many machines fast and quite frankly script the lot so
I don't have to do it twice.

So my advice stands
Buy a book on batch scripting
learn how ruby works.

if you're provisioning a server the idea is that you're in control of where
you download and extract the zip.
so you know and it will probably be the same on another server you create
and provision with your script (rocket science, I think not) killing the
need for a preordained location which probably isn't where I want it.
You don't even need to set the path and if you're running a script it's easy
to do so in the script.



---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)



On Mon, Jan 25, 2010 at 7:50 PM, Mohammad Azam <li...@ruby-forum.com> wrote:

> The problem is that every person has their own IronRuby folder. It has
> to work same for everyone. Kind of like libraries in GAC.
>
> You are NOT thinking throughly about the problem!
>
> This is not regarding putting the path in ENV variables and copying
> couple of files. This is about doing the same thing for 10 servers. I
> don't think you will be comfortable doing the same for 10 servers.
>
> This also adds extra work for writing build scripts that will do this
> work.
>
> Maybe the IronRuby installation should add the IronRuby folder to a
> common path which is same for all the machines. Kind of like when
> installing the .NET framework which is usually on a common place.
>
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core@rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Reply via email to