marcuscom and www/epiphany-extensions

[Koop Mast]

On Thu, 2010-02-25 at 16:13 +0100, varga.michal at gmail.com wrote:
> On Thu, Feb 25, 2010 at 2:47 PM, Joe Marcus Clarke <marcus at freebsd.org> wrote:
> > On 2/25/10 6:18 AM, varga.michal at gmail.com wrote:
> >> Hello guys,
> >>
> >> it's been quite some months into the 2.29 development cycle, and there
> >> is still no www/epiphany-extensions on marcuscom to be seen. Is there
> >> something wrong that prevents it from being ported, or it's just an
> >> oversight / lack of manpower? (In that case, I could do it.)
> >
> > As far as I know, it's an oversight.  I didn't notice an update.  kwm,
> > avl, or ahze may have tried to build it, and ran into problems, but I
> > was not made aware.  If you want to do the port, that would be great.
> >
> 
> Well, while generating temporary plist, I noticed that
> epiphany-extensions actually doesn't honor PREFIX, probably because of
> this line in configure:
> 
> EPIPHANY_EXTENSIONS_DIR="$($PKG_CONFIG --variable=extensionsdir
> epiphany-$_epiphany_api_version)"
> 
> ..which obviously points to:
> 
> > pkg-config --variable=extensionsdir epiphany-2.29
> /usr/local/lib/epiphany/2.29/extensions
> 
> ..where libraries get installed, no matter of PREFIX. Also from the
> quick glance it seems to me that the same issue is present in the
> current 2.28.x port, which strikes me odd as I was under impression
> that tinderbox runs tend to catch those.
> 
> Anyway - what is the correct way to solve this, or possibly - am I
> missing something in the big picture?
> 
> m.

Tinderbox will not catch this, because it uses the same prefix for
epiphany and epiphany-extensions. About the lack of updates to this
port, marcus is correct. It just fell though the cracks. Now that is
known we missed a port, one of us will fix that soonish. Or do you want
to do the work?

-Koop