Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Aug 2011 13:22:55 +0100
From:      Chris Rees <utisoft@gmail.com>
To:        "Conrad J. Sabatier" <conrads@cox.net>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: audio/amarok: make TRYBROKEN=yes reinstall worked!
Message-ID:  <CADLo838A8AdcxwvkANx_VwPNVU%2Bnr62ivQZtbhH9tigUW77KOA@mail.gmail.com>
In-Reply-To: <20110827050955.12b8e369@cox.net>
References:  <20110827035245.7c7676a8@cox.net> <4E58B2F2.7070809@gmx.de> <20110827050955.12b8e369@cox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Aug 2011 11:10, "Conrad J. Sabatier" <conrads@cox.net> wrote:
>
> On Sat, 27 Aug 2011 11:03:46 +0200
> Matthias Andree <matthias.andree@gmx.de> wrote:
>
> > Am 27.08.2011 10:52, schrieb Conrad J. Sabatier:
> > > As the subject line states, I just managed to rebuild and reinstall
> > > audio/amarok with no glitches whatsoever.
> > >
> > > # uname -a
> > > FreeBSD serene.no-ip.org 9.0-BETA1 FreeBSD 9.0-BETA1 #7: Thu Aug 25
> > > 01:47:03 CDT 2011
> > > conrads@serene.no-ip.org:/usr/obj/usr/src/sys/CUSTOM  amd64
> > >
> > > So, what exactly is broken about this port?
> > >
> >
> > Reading the actual output or the Makefile helps:
> >
> > .if ${RUBY_VER} == 1.9
> > BROKEN=       does not build with ruby 1.9
> > .endif
>
> Well, yes, of course, I saw that, but the port does, in fact, build
> just fine.
>
> > So, related questions:
> >
> > - is Ruby 1.9 the only Ruby version on your system?
>
> No, I have both 1.8 and 1.9.
>
> > - does your newly-built Amarok _use_ Ruby? Or did the configuration or
> > build weazel out of it?
> >
> > - do Ruby-related features _work properly_ in your Amarok build?
> >
> > Then and only then we can remove this BROKEN= tag.
>
> # pkg_info -r amarok-1.4.10_14|grep ruby
> Dependency: ruby-1.9.2.290_1,1
>
> I know at least one amarok script bugs out on me (lyric-wiki).  But
> otherwise, functionality seems quite normal.
>
> Couldn't we use a USE_RUBY=1.8 knob or something, if necessary?
>
> I'm personally of the opinion that if a particular script won't work
> with ruby 1.9, it's the script that needs fixing.  YMMV.

Hm, just because the ports system registered the dependency that way doesn't
guarantee it was built against 1.9. To properly test, one must have only 1.9
installed.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838A8AdcxwvkANx_VwPNVU%2Bnr62ivQZtbhH9tigUW77KOA>