[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Any tips or guidelines for creating ruby packages?
- From: Jeff Spaleta <jspaleta gmail com>
- To: "Tom 'spot' Callaway" <tcallawa redhat com>, Discussion related to Fedora Extras <fedora-extras-list redhat com>
- Cc:
- Subject: Re: Any tips or guidelines for creating ruby packages?
- Date: Thu, 28 Jul 2005 12:40:04 -0400
On 7/27/05, Tom 'spot' Callaway <tcallawa redhat com> wrote:
> Package it up, and I'll look it over. If we need to make packaging
> policy changes, I'll help.
first draft package that doesn't make any attempt yet to split off
individual library bindings into seperate subpackages available at:
http://jef.is--a-geek.com/downloads/ruby-gnome2-all/
I've built this in mock against x86 fc4
Clearly I'm going to want to split out the binary subpackages based on
individual subdirectories of the full source tarball... tedious but
not difficult to do.
I'm more concerned about how rpm is catching the provided so files.
There's no indication that the provides are libraries in ruby's site
directory as compared to system lbraries. Is this going to be a
problem?
-jef
rpm -q --provides -p ruby-gnome2-all/ruby-gnome2-all-0.12.0-1.i386.rpm
atk.so
gconf2.so
gdk_pixbuf2.so
glib2.so
gnome2.so
gnomecanvas2.so
gnomeprint2.so
gnomeprintui2.so
gnomevfs.so
gst.so
gtk2.so
gtk20.so
gtk22.so
gtkglext.so
gtkhtml2.so
gtksourceview.so
libart2.so
libgda.so
libglade2.so
panelapplet2.so
pango.so
rsvg2.so
ruby-gnome2-all = 0.12.0-1
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]