[Rubygems-developers] Two feature requests

Austin Ziegler halostatue at gmail.com
Thu Sep 23 10:35:55 EDT 2004

On Thu, 23 Sep 2004 07:28:15 -0500, Curt Hibbs <curt at hibbs.com> wrote:
> Mehr, Assaph wrote:
> >
> > In this case I am concerned about distributing applications, and not
> > libraries. The target audience is also different: not (paranoid)
> > developers. If people choose to install my app, they are likely to trust
> > me and my code. At that point I want to give them a nice integrated
> > solution, something that will install the app on their system as a
> > regular application.
> >
> > The app-gem-installer currently has 2 modes: One which generates an NSIS
> > script, from which I can generate and .exe installer (and pack the gem
> > within it); and second which is a ruby script that does all the
> > shortcuts, file-associations etc.
> > What I want is simply to allow running this as a post install step.
> >
> > Never underestimate coveniences and leaky abstractions. They tend to be
> > powerful with myriad usages. Just look at Ruby ;-)
> Maybe it would be better if your app-gem-installer was run as the top-level
> script and just used rubygems with in it. That way you are in control and
> can run any pre or post installation steps you like.

If coupled with the "gem run <gemname> <execfile>" concept, esp. if
this functionality is made available programmatically, then the
app-gem-installer could do this as a functionality option:

  if %x{gem has <gemname> <execfile>} then %x{gem run <gemname> <execfile>}

Austin Ziegler * halostatue at gmail.com
               * Alternate: austin at halostatue.ca
: as of this email, I have [ 6 ] Gmail invitations

More information about the Rubygems-developers mailing list