Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-gnome Digest, Vol 358, Issue 9

0 views
Skip to first unread message

freebsd-gn...@freebsd.org

unread,
Mar 6, 2010, 7:00:17 AM3/6/10
to freebs...@freebsd.org
Send freebsd-gnome mailing list submissions to
freebs...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
or, via email, send a message with subject or body 'help' to
freebsd-gn...@freebsd.org

You can reach the person managing the list at
freebsd-g...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-gnome digest..."


Today's Topics:

1. Re: marcuscom and www/epiphany-extensions (Koop Mast)


----------------------------------------------------------------------

Message: 1
Date: Fri, 05 Mar 2010 15:47:30 +0100
From: Koop Mast <k...@FreeBSD.org>
Subject: Re: marcuscom and www/epiphany-extensions
To: Michal Varga <varga....@gmail.com>
Cc: gn...@freebsd.org, Joe Marcus Clarke <mar...@freebsd.org>
Message-ID: <1267800450.9...@headache.rainbow-runner.nl>
Content-Type: text/plain; charset="us-ascii"

On Thu, 2010-03-04 at 05:19 +0100, Michal Varga wrote:
> Well, as I received no reply to my last email for a while, I opted for
> a "do as you wish" answer and here is my try at a slightly revamped
> epiphany-extensions.
>
> The major focus is PREFIX compliance, which I was able to achieve only
> by working around a few pkgconfig variables (that ephy-extensions
> hijacks in a way that currently makes the port uninstallable, see my
> previous emails). While my solution surely isn't the best possible,
> every other I came up with involves some unholy on-the-fly regexp
> magic around epiphany's pkgconfig that doesn't make me very
> comfortable for some reason.
>
> Anyway - I crosschecked with epiphany's *.pc as for how the original
> paths are built and this replacement is (should be) perfectly safe,
> thus making the port not silently installing files outside specified
> PREFIX and still properly working at the same time. The only downside
> is, that with -extensions and epiphany installed both in different
> prefixes (which doesn't happen in real life), extensions will not
> work, for obvious reasons (but package de/installation will not be
> broken, as it is now). I would consider that the lesser evil.
>
> For the rest of the changes, I've been testing the port thoroughly and
> enabled all available extensions, this makes stuff like mouse gestures
> and greasemonkey actually available. Then there is an updated
> pkg-descr and I think that's probably it. Let me know if there is
> something that shouldn't be.
>
> Also, if there will be no objections, I'd like to continue updating
> ephy-extensions in the future, for both marcuscom and stable ports -
> of course, if there is no one else who explicitly wants to do it, for
> some reason.
>
> m.
>

Thanks for the work. I committed it to MC with some minor tweaks.
About updating, we will pick it up when it get released. Or if a release
of any gnome port goes unnoticed, feel free to poke any of us about it.

-Koop

<snip shar>

------------------------------

End of freebsd-gnome Digest, Vol 358, Issue 9
*********************************************

0 new messages