Fixup the Snake eggs too please (i.e. Python eggs aren't building on CentOS 5.5 
grr ...)

hth

73 de Jeff

On Oct 16, 2010, at 5:57 PM, Per Øyvind Karlsen wrote:

>  RPM Package Manager, CVS Repository
>  http://rpm5.org/cvs/
>  ____________________________________________________________________________
> 
>  Server: rpm5.org                         Name:   Per Øyvind Karlsen
>  Root:   /v/rpm/cvs                       Email:  [email protected]
>  Module: rpm                              Date:   16-Oct-2010 23:57:24
>  Branch: rpm-5_3                          Handle: 2010101621572400
> 
>  Modified files:           (Branch: rpm-5_3)
>    rpm/macros              ruby.in
> 
>  Log:
>    pass --ignore-dependencies to gem during install
> 
>  Summary:
>    Revision    Changes     Path
>    1.1.2.4     +1  -1      rpm/macros/ruby.in
>  ____________________________________________________________________________
> 
>  patch -p0 <<'@@ .'
>  Index: rpm/macros/ruby.in
>  ============================================================================
>  $ cvs diff -u -r1.1.2.3 -r1.1.2.4 ruby.in
>  --- rpm/macros/ruby.in       16 Oct 2010 10:03:52 -0000      1.1.2.3
>  +++ rpm/macros/ruby.in       16 Oct 2010 21:57:24 -0000      1.1.2.4
>  @@ -37,7 +37,7 @@
>   %gem_install(i:n:C) \
>       DESTDIR=${DESTDIR:-%{buildroot}} \\\
>       %__gem_helper install \\\
>  -    --env-shebang --rdoc --ri --force \\\
>  +    --env-shebang --rdoc --ri --force --ignore-dependencies \\\
>       %{!-i:--install-dir %{buildroot}%{ruby_gemdir}}%{-i:--install-dir 
> %{-i*}} \\\
>       %{!-n:--bindir %{buildroot}%{_bindir}}%{-n:--bindir%{-n*}} \\\
>       %{!-C:--fix-permissions}
>  @@ .
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> CVS Sources Repository                                [email protected]

______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        [email protected]

Reply via email to