Patrick Hurley
5/24/2007 3:08:00 PM
On 5/24/07, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
> It can be even weirder than that. I often have to ship extension gems for
> multiple versions of glibc, the crypto libraries, etc. The platform version
> string is always i686-linux or some such thing, but they're still distinct
> (and incompatible) binary gems. Even with gembuilder, I'll need to decorate
> the gem filenames by hand. Still, it's a huge help. Up till now, I've had to
> keep extra rake tasks around for each of my target platforms and
> subplatforms.
>
Yeah I was initially put off by the mac showing the platform as
darwin8.9.1, but I realized that was how it would avoid those sort of
glibc issues. It might be better if Linux was expanded out to
linux.glibc.4 or something to that effect, but I am (obviously?)
riding on the information in rbconfig.
I am in the simple position where I deploy to a large number of
homogeneous servers for a given client (although the platform will
vary client to client). So this is not a hardship for me. If anyone
has a solution/suggestion for better handling the wide variety of
binary combinations I would be happy to try and integrate it.
Would something as simple as allowing a command line option or
environment variable to set a user defined platform name be useful?
pth