RubyGems pre/post install

Does RubyGems support pre/post install scripting?

T.

nope.

-a

···

On Mon, 26 Mar 2007, Trans wrote:

Does RubyGems support pre/post install scripting?

--
be kind whenever possible... it is always possible.
- the dalai lama

Not sure if 'support' is the right word. :slight_smile:

···

On 3/25/07, Trans <transfire@gmail.com> wrote:

Does RubyGems support pre/post install scripting?

And with, I think, very good reason. There are times when, in the
past, I wished it did, but aside from one loophole, there's no way to
get a gem to execute arbitrary code on installation.

-austin

···

On 3/25/07, ara.t.howard@noaa.gov <ara.t.howard@noaa.gov> wrote:

On Mon, 26 Mar 2007, Trans wrote:
> Does RubyGems support pre/post install scripting?
nope.

--
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
               * austin@halostatue.ca * http://www.halostatue.ca/feed/
               * austin@zieglers.ca

Thanks Ara, Gregory and Austin. Guess, I'll just write gembundle as an
extension to Gems then.

T.

···

On Mar 25, 12:48 pm, "Austin Ziegler" <halosta...@gmail.com> wrote:

On 3/25/07, ara.t.how...@noaa.gov <ara.t.how...@noaa.gov> wrote:

> On Mon, 26 Mar 2007, Trans wrote:
> > Does RubyGems support pre/post install scripting?
> nope.

And with, I think, very good reason. There are times when, in the
past, I wished it did, but aside from one loophole, there's no way to
get a gem to execute arbitrary code on installation.

-austin
--
Austin Ziegler * halosta...@gmail.com *http://www.halostatue.ca/
               * aus...@halostatue.ca *http://www.halostatue.ca/feed/
               * aus...@zieglers.ca

Actually, there are two. I'm going to remove the second one sometime soon.

···

On Mar 25, 2007, at 09:48, Austin Ziegler wrote:

On 3/25/07, ara.t.howard@noaa.gov <ara.t.howard@noaa.gov> wrote:

On Mon, 26 Mar 2007, Trans wrote:
> Does RubyGems support pre/post install scripting?
nope.

And with, I think, very good reason. There are times when, in the
past, I wished it did, but aside from one loophole, there's no way to
get a gem to execute arbitrary code on installation.