-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 02 November 2010, Jeff Johnson n3...@mac.com wrote:
Apologies. But somehow a common (between HEAD - rpm-5_3) approach
to the needed ruby AutoFu needs to be devised. What was/is on the
rpm-5_3 branch permitted me to build against both
On Nov 6, 2010, at 9:49 AM, Eric MSP Veith wrote:
So either revert on HEAD (ask if you need the cvs commands), or
make peace with the ruby AutoFu in rpm-5_3.
I wasn't able to build with what was previously there, and I have no crude
setup but a vanilly Ruby installed with standard paths
Is there any way to ship files to be %included that's more convenient
than the following:
Source1: somestuff
%include %{SOURCE1}
The problem with this is that if the spec file is queried without the
correct %_sourcedir set, it will fail.
If one could do something like 'Source1:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 06 November 2010, Jeff Johnson n3npq@gmail.com wrote:
OK. I can/will drill in whatever AutoFu is needed.
Ok, thanks! Alternatively, I can come up with a small Ruby script that works
like ruby-config and put it somewhere in the RPM
On Nov 6, 2010, at 11:25 AM, Per Øyvind Karlsen wrote:
Is there any way to ship files to be %included that's more convenient
than the following:
Source1: somestuff
%include %{SOURCE1}
The problem with this is that if the spec file is queried without the
correct %_sourcedir set, it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 06 November 2010, Jeff Johnson n3npq@gmail.com wrote:
Ick, not a ruby script to find ruby please.
Thing is that there's currently no way to get configure-time information
about ruby from ruby except with ruby code. :-(
I checked
On Nov 6, 2010, at 12:56 PM, Eric MSP Veith wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May not matter for yr bindings, but it most definitely matters
when RPM builds needs all the correct AutoFu in place to build.
AFAIK, there's no difference between 1.9.x and 1.8.x when
On Nov 6, 2010, at 11:25 AM, Per Øyvind Karlsen wrote:
Is there any way to ship files to be %included that's more convenient
than the following:
Source1: somestuff
%include %{SOURCE1}
The problem with this is that if the spec file is queried without the
correct %_sourcedir set, it will
