Including other people's Ruby libs in your package

ruby-talk
1

I would prefer that people be able to just download a tarball,
extract it, and copy over a directory to the libs dir. And it just

works.

On the other hand, it can be very annoying for a user as well when
they already have a *newer* version of that same dependency

installed,

and then they install your library and suddenly things break.

That question is, What's the best way?

What are your target audience?
Developers/power-user would like control over what goes in.
Grandmas like everything to work with minimum hassel.

Tailor your solution (and it's robustness) to your audience.

My 2c.

2

Mehr, Assaph (Assaph) wrote:

That question is, What's the best way?

What are your target audience?
Developers/power-user would like control over what goes in.
Grandmas like everything to work with minimum hassel.

Tailor your solution (and it's robustness) to your audience.

Both. Complete control with a minimum of fuss (why must there be a choice?).

My hope would be such that there would at least be a default lib installed, but that it would not take precedence over any existing files, not stop anyone from simply installing a preferred version.

ยทยทยท

My 2c.