wxruby users - Nov 2003 - Gentoo ebuild

Hi!

Since I switched from SuSE to Gentoo (before Novell era :-) I wrote a simple
ebuild script for building wxruby on Gentoo.

Few notes:

a) in order to work, wxruby-0.1.0.tgz should contain wxruby-0.1.0 folder since
it is a Gentoo policy and I hope it''s not a problem to change that for
0.2.0

b) I assumed that one needs Ruby >= 1.8.0 and wx >= 2.4.1. Is it OK?

Please inspect ebuild and give me your feedback. Later we can fix it and put
it under Gentoo''s bugzilla in order to become part of unstable Portage
tree,
and later - hopefully - part of the official Gentoo distribution.

Here is the ebuild:

------ cut-here ------------------------------------------
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: $


DESCRIPTION="wxRuby are Ruby language bindings for wxWindows GUI
toolkit"
HOMEPAGE="http://rubyforge.org/projects/wxruby/"
SRC_URI="http://rubyforge.org/download.php/60/wxruby-0.1.0.tgz"
LICENSE="wxWinLL-3"
SLOT="0"
KEYWORDS="~x86"
IUSE=""
DEPEND=">=dev-lang/ruby-1.8.0
        >=x11-libs/wxGTK-2.4.1"

src_compile() {
   if [ `use unicode` ];
   then
       einfo "wxruby needs wxGTK compiled without
''unicode'' support."
       einfo "Please re-emerge wxGTK."
       die
   else
       cd src
       ruby extconf.rb || die
       make || die
   fi
}

src_install() {
   cd src
   DESTDIR=${D}
   make install || die
   dodoc ../ChangeLog ../README ../README.linux ../README.mingw ../README.mswin
../README.osx
}

------ cut-here -------------------------------------------

Sincerely,
Gour

-- 
Gour
gour@mail.inet.hr
Registered Linux User #278493

Gour wrote:
> Since I switched from SuSE to Gentoo (before Novell era :-) I wrote a
simple
> ebuild script for building wxruby on Gentoo.
Excellent. Thanks.
> a) in order to work, wxruby-0.1.0.tgz should contain wxruby-0.1.0 folder
since
> it is a Gentoo policy and I hope it''s not a problem to change that
for 0.2.0
So you''re saying that the top level of the tgz would be just a 
wxruby-0.2.0 directory, and everything else would be under that?
> b) I assumed that one needs Ruby >= 1.8.0 and wx >= 2.4.1. Is it OK?
I believe wxruby still works with Ruby 1.6.8, but gentoo folks are known 
for living on the bleeding edge, so 1.8.0 might be better.
> Please inspect ebuild and give me your feedback. Later we can fix it and
put
> it under Gentoo''s bugzilla in order to become part of unstable
Portage tree,
> and later - hopefully - part of the official Gentoo distribution.
That would be great. I don''t know anything about ebuilds, but I
didn''t
see any problems with what you sent. Would this ebuild go inside the 
tarball somewhere? Or is it strictly external? Either way, I assume we 
should check it into CVS, so we''ll need to give it a name and decide 
what directory it belongs in.

Kevin

Kevin Smith (wxRuby@qualitycode.com) wrote:
> So you''re saying that the top level of the tgz would be just a 
> wxruby-0.2.0 directory, and everything else would be under that?
Yes, instead of the present: wxruby-0.1.0.tgz --> wxruby --> samples
                                                         |
							 --> src

it should be something like: wxruby-0.1.0.tgz --> wxruby-0.1.0 --> samples
                                                               |
							       --> src

Not a big change, isn''t it?
> I believe wxruby still works with Ruby 1.6.8, but gentoo folks are known 
> for living on the bleeding edge, so 1.8.0 might be better.
True. I''m also not sure whether is 1.6.8 still present in Portage.
> That would be great. I don''t know anything about ebuilds, but I
didn''t
> see any problems with what you sent. Would this ebuild go inside the 
> tarball somewhere? Or is it strictly external? Either way, I assume we 
> should check it into CVS, so we''ll need to give it a name and
decide
> what directory it belongs in.
Usually, we need to submit ebuild (with the email of maintainer) as a Gentoo
bug (''cause it''s still unstable), and then I can inform folks
in Gentoo forums
about it.

There is no need to put ebuild within tarball, since Gentoo philosophy is that
''emerge wxruby'' command should do the whole job ie. fetch,
compile, install &
integrate in the system.

Most important is that the structure of tarball is changed, otherwise it cannot
be built.

Of course, it is possible to write ebuild to handle ''wxruby''
folder instead of
wxruby-0.1.0, but I consider it is not a big change and it is more consistent
(not only for Gentoo needs.)

So, let me know when you change tarball (it can be 0.1.1 :-) so I can test the 
ebuild live :-)


Sincerely,
Gour

ps. I forgot about the license - I put it as wxWinLL-3. Is it a correct one?

-- 
Gour
gour@mail.inet.hr
Registered Linux User #278493