Issue about adapting japanese/ruby-mecab to new options framework

Yasuhiro KIMURA yasu at utahime.org
Mon Jan 28 09:30:44 UTC 2013


From: Jason Helfman <jgh at FreeBSD.org>
Subject: Re: Issue about adapting japanese/ruby-mecab to new options framework
Date: Sun, 27 Jan 2013 11:40:04 -0800

> You could look at setting OPTIONSFILE in the ports Makefile, itself.
> For instance, this is set in net/rubygem-net-ssh. Although this may not be
> the exact entry, this is an example you can work with to get it to work as
> it should.
>
> OPTIONSFILE?=   ${PORT_DBDIR}/rubygem-${PORTNAME}/options

From: Scot Hetzel <swhetzel at gmail.com>
Subject: Re: Issue about adapting japanese/ruby-mecab to new options framework
Date: Sun, 27 Jan 2013 13:41:00 -0600

> You could add OPTIONSFILE to japanese/ruby-mecab/Makefile as:
>
> OPTIONSFILE=	${PORT_DBDIR}/ruby-mecab/options
>
> This way it will always find it's own options file.

When following line is added in japanese/ruby-mecab/Makefile, options
dialog doesn't displayed only once:

OPTIONSFILE=	${PORT_DBDIR}/ja-ruby-mecab/options

But when following line is added, it displayed every time:

OPTIONSFILE=	   ${PORT_DBDIR}/ja-${RUBY_PKGNAMEPREFIX}${PORTNAME}/options

Does it mean RUBY_PKGNAMEPREFIX cannot be used to assign OPTIONSFILE?
If answer is yes then the former is best solution. But if possible I
would like to reflect the version of ruby on OPTIONSFILE.

---
Yasuhiro KIMURA


More information about the freebsd-ports mailing list