gembundles

Hi--

A few days back I brought up some ideas for dealing with
multi-packages. This evening I sat down and put to together
a little
tool to handle just that: gembundle.

The ideas is simple. Lets say I have a couple of gems:
hello_world.gem
and adios_world.gem.

  % gembundle build tryme hello_world-1.0.0.gem
adios_world-1.0.0.gem

This creates a tar.gz file called, tryme.gembundle which
simply
contains the two listed gems, Then...

  % gembundle install tryme.gembundle
  Successfully installed hello_world, version 1.0.0
  Successfully installed adios_world, version 1.0.0

The intsall command just copies the bundle to a temp
location, unpacks
it and installs the contained gems (with the -y option).

That's it.

Of course, my script is just a quick prototype --I'm
shelling out for
all the tar and gem stuff. And it doesn't support some
features like
remote access for grabbing gems to bundle.  But hopefully it
doesn't
matter b/c I wanted to see if others would approve of this
functionality being incorporated into RubyGems itself. It's
pretty
straightforward. It would just mean adding a
"bundle" command to the
gem CLI and allowing the installer to recognize a bundle vs
a regular
gem,such that '.gem' could still be used instead
'.gembundle'.

So what is it good for? It gives large application
developers
breathing room to use vendor gems more freely. Per my
explanation in
my last post, installing a gem that has many dependencies
can be
off-putting. Not only does the administrator have to
consider each
dependency, but ensuring the right versions of each can be
daunting as
well.  Gembundles take care these concerns. And since a
bundle simply
contains regular gems it works seamlessly with the current
design.

What do you think?

Thanks,
T.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/20/07, TRANS <transfiregmail.com> wrote:
> Hi--
>
> A few days back I brought up some ideas for dealing
with
> multi-packages. This evening I sat down and put to
together a little
> tool to handle just that: gembundle.
>
> The ideas is simple. Lets say I have a couple of gems:
hello_world.gem
> and adios_world.gem.
>
>   % gembundle build tryme hello_world-1.0.0.gem
adios_world-1.0.0.gem
>
> This creates a tar.gz file called, tryme.gembundle
which simply
> contains the two listed gems, Then...
>
>   % gembundle install tryme.gembundle
>   Successfully installed hello_world, version 1.0.0
>   Successfully installed adios_world, version 1.0.0
>
> The intsall command just copies the bundle to a temp
location, unpacks
> it and installs the contained gems (with the -y
option).
>
> That's it.
>
> Of course, my script is just a quick prototype --I'm
shelling out for
> all the tar and gem stuff. And it doesn't support some
features like
> remote access for grabbing gems to bundle.  But
hopefully it doesn't
> matter b/c I wanted to see if others would approve of
this
> functionality being incorporated into RubyGems itself.
It's pretty
> straightforward. It would just mean adding a
"bundle" command to the
> gem CLI and allowing the installer to recognize a
bundle vs a regular
> gem,such that '.gem' could still be used instead
'.gembundle'.
>
> So what is it good for? It gives large application
developers
> breathing room to use vendor gems more freely. Per my
explanation in
> my last post, installing a gem that has many
dependencies can be
> off-putting. Not only does the administrator have to
consider each
> dependency, but ensuring the right versions of each can
be daunting as
> well.  Gembundles take care these concerns. And since a
bundle simply
> contains regular gems it works seamlessly with the
current design.
>
> What do you think?

No response?

T.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/21/07, Nic Williams <drnicwilliamsgmail.com> wrote:
> I'll bite.
>
> One popular bundle people might relate to is to bundle
the rails gems
> together, as a demonstration.
>
> BTW, does/will your solution work for gems with
components that get compiled
> at installation time? Probably not a showstopper
though,. Gembundle still
> seems a good idea.

I don't see why not. It installs gems just like gems are
currently
installed, this just adds a layer for packaging packages
--hence a
literal multi-package.

Thanks for the support. I hope others feel the same. I
especially
would like to know what the gem developers think, as I
really need
this functionality, like, yesterday 

T.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/22/07, TRANS <transfiregmail.com> wrote:
> On 3/21/07, Nic Williams <drnicwilliamsgmail.com> wrote:
> > I'll bite.
> >
> > One popular bundle people might relate to is to
bundle the rails gems
> > together, as a demonstration.
> >
> > BTW, does/will your solution work for gems with
components that get compiled
> > at installation time? Probably not a showstopper
though,. Gembundle still
> > seems a good idea.
>
> I don't see why not. It installs gems just like gems
are currently
> installed, this just adds a layer for packaging
packages --hence a
> literal multi-package.

But they are built on the target system correct? I am
actually (when I
can find spare minutes) working on a binary builder, that
will take a
built from source binary gem from one system and create a
new binary
gem for that architecture. It is not elegant (I package up
intermediate object files and the like), but in general I
believe it
will work. This is to simplify the use of gems with
extensions on
production servers that do not generally have a C compiler
or other
build tools.

pth
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/22/07, Patrick Hurley <phurleygmail.com> wrote:
> On 3/22/07, TRANS <transfiregmail.com> wrote:
> > On 3/21/07, Nic Williams <drnicwilliamsgmail.com> wrote:
> > > I'll bite.
> > >
> > > One popular bundle people might relate to is
to bundle the rails gems
> > > together, as a demonstration.
> > >
> > > BTW, does/will your solution work for gems
with components that get compiled
> > > at installation time? Probably not a
showstopper though,. Gembundle still
> > > seems a good idea.
> >
> > I don't see why not. It installs gems just like
gems are currently
> > installed, this just adds a layer for packaging
packages --hence a
> > literal multi-package.
>
> But they are built on the target system correct? I am
actually (when I
> can find spare minutes) working on a binary builder,
that will take a
> built from source binary gem from one system and create
a new binary
> gem for that architecture. It is not elegant (I package
up
> intermediate object files and the like), but in general
I believe it
> will work. This is to simplify the use of gems with
extensions on
> production servers that do not generally have a C
compiler or other
> build tools.

Since I don't write any c code I am not aware. Gems doesn't
have a
facility for compiling? I though t did. Well, however Gems
works is
how Gembundles would work too. It just adds an extra
multiple-package
delivery layer.

T.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On Mar 20, 2007, at 18:39, TRANS wrote:
> A few days back I brought up some ideas for dealing
with
> multi-packages. This evening I sat down and put to
together a little
> tool to handle just that: gembundle.
>
> [...]
>
> Of course, my script is just a quick prototype --I'm
shelling out for
> all the tar and gem stuff. And it doesn't support some
features like
> remote access for grabbing gems to bundle.  But
hopefully it doesn't
> matter b/c I wanted to see if others would approve of
this
> functionality being incorporated into RubyGems itself.
It's pretty
> straightforward. It would just mean adding a
"bundle" command to the
> gem CLI and allowing the installer to recognize a
bundle vs a regular
> gem,such that '.gem' could still be used instead
'.gembundle'.
>
> So what is it good for? It gives large application
developers
> breathing room to use vendor gems more freely. Per my
explanation in
> my last post, installing a gem that has many
dependencies can be
> off-putting. Not only does the administrator have to
consider each
> dependency, but ensuring the right versions of each can
be daunting as
> well.  Gembundles take care these concerns. And since a
bundle simply
> contains regular gems it works seamlessly with the
current design.
>
> What do you think?

Why not release it as a separate gem, let it develop for a
while, and  
if people use it, it can be included in RubyGems at a future
date?

Bundling with RubyGems is going to reduce opportunities for
rapid  
improvement.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On Mar 22, 2007, at 08:17, Patrick Hurley wrote:
> On 3/22/07, TRANS <transfiregmail.com> wrote:
>> On 3/21/07, Nic Williams <drnicwilliamsgmail.com> wrote:
>>> I'll bite.
>>>
>>> One popular bundle people might relate to is to
bundle the rails  
>>> gems
>>> together, as a demonstration.
>>>
>>> BTW, does/will your solution work for gems with
components that  
>>> get compiled
>>> at installation time? Probably not a
showstopper though,.  
>>> Gembundle still
>>> seems a good idea.
>>
>> I don't see why not. It installs gems just like
gems are currently
>> installed, this just adds a layer for packaging
packages --hence a
>> literal multi-package.
>
> But they are built on the target system correct? I am
actually (when I
> can find spare minutes) working on a binary builder,
that will take a
> built from source binary gem from one system and create
a new binary
> gem for that architecture. It is not elegant (I package
up
> intermediate object files and the like), but in general
I believe it
> will work. This is to simplify the use of gems with
extensions on
> production servers that do not generally have a C
compiler or other
> build tools.

RubyInline has this capability.

_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/23/07, Eric Hodel <drbrainsegment7.net> wrote:

> Why not release it as a separate gem, let it develop
for a while, and
> if people use it, it can be included in RubyGems at a
future date?
>
> Bundling with RubyGems is going to reduce opportunities
for rapid
> improvement.

Okay. Well I can do that. It's pretty drop-dead simple
though. Do you
have any reason to suspect it's a bad idea?

I'll go ahead and make it available, I'd want to use Gems
built-in
functions though. How would I use Gems lib to create a
tarball?

Thanks,
T.
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs

On 3/23/07, TRANS <transfiregmail.com> wrote:
> On 3/23/07, Eric Hodel <drbrainsegment7.net> wrote:
> > Why not release it as a separate gem, let it
develop for a while, and
> > if people use it, it can be included in RubyGems
at a future date?

> > Bundling with RubyGems is going to reduce
opportunities for rapid
> > improvement.
> Okay. Well I can do that. It's pretty drop-dead simple
though. Do you
> have any reason to suspect it's a bad idea?

Yeah; it's shelling out for tar. Use Archive::Tar::Minitar
instead and
then you only depend on RubyGems and can script that
appropriately
(see Patrick's questions recently on automating Gems).

-austin
-- 
Austin Ziegler * halostatuegmail.com * http://www.halostatue.ca/
               * austinhalostatue.ca * http://www.halostatue.
ca/feed/
               * austinzieglers.ca
_______________________________________________
Rubygems-developers mailing list
Rubygems-developersrubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-develope
rs