From owner-freebsd-ports@FreeBSD.ORG  Mon Aug  5 21:13:29 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 92426D1E
 for <freebsd-ports@freebsd.org>; Mon,  5 Aug 2013 21:13:29 +0000 (UTC)
 (envelope-from mwisnicki@gmail.com)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com
 [IPv6:2607:f8b0:4003:c01::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5B67C28A7
 for <freebsd-ports@freebsd.org>; Mon,  5 Aug 2013 21:13:29 +0000 (UTC)
Received: by mail-ob0-f181.google.com with SMTP id dn14so6769143obc.12
 for <freebsd-ports@freebsd.org>; Mon, 05 Aug 2013 14:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=rUq0wRSdguBi0vlTBfY9S7jhrUNXNmtF5HR6fEODPKo=;
 b=ULwvw1H5UIJ+Z28voEbnByP0fa86fniDQjb7AOHOABaAfrL9hcju9szl/xqobMR017
 wTsgyhTyLrxN2dmV1AIA237XPLsPnd/3wfNZYtiY+9qBOZZHFDgPWG04TIBSHpwHFsYe
 7aCtI+M65Hk/L7ESo4nbQ2DqEkl5uF1j9bKuawEdZyIw7eSsBkPjTdobiuWRxZeQjtro
 4/PEeC5hMp8bwmK9Y5FhBQXEF4poAXbMaj2YaX4h5prDClYhK1ly/m+nNiiIjqq0uj0x
 S8oFNVaYyDlUFfvNSauUE3B1sRYRySte73iN0G9WUk5SELfbjh7NYEa6u29bhILm9UIU
 yimw==
MIME-Version: 1.0
X-Received: by 10.182.119.229 with SMTP id kx5mr15872441obb.23.1375737208511; 
 Mon, 05 Aug 2013 14:13:28 -0700 (PDT)
Sender: mwisnicki@gmail.com
Received: by 10.76.19.40 with HTTP; Mon, 5 Aug 2013 14:13:28 -0700 (PDT)
In-Reply-To: <CAJ_iqtbOUr0+8D-6uXEVbzqzHLy4i=Mk=4D76LXboBW_wUS8sg@mail.gmail.com>
References: <CAJ_iqtbfe_HJEiEfeFQLvA=r=NC2GsGqOm+2UKF+eosuimK1ng@mail.gmail.com>
 <CAC9GOO9Xz+3EqBrkLyrSVo+BwENE-chf0iOMSKm9fPd=8dzJYw@mail.gmail.com>
 <CAJ_iqtZ9h5e=57C94wBiZmcHXGUKq-dfTAGN6H4N2Z_fbb8gnQ@mail.gmail.com>
 <CAC9GOO-HEFvvkgu-Nc80vNFhFq_eZWJ8vLusm8A3Gf__x82cJA@mail.gmail.com>
 <CAJ_iqtbOUr0+8D-6uXEVbzqzHLy4i=Mk=4D76LXboBW_wUS8sg@mail.gmail.com>
Date: Mon, 5 Aug 2013 23:13:28 +0200
X-Google-Sender-Auth: KALklWIPSpGgwrsxvJd2QAxS60E
Message-ID: <CAC9GOO98attj_AZx0caJbsUqHtS52szqK8WBi729yQ2YFAiRcQ@mail.gmail.com>
Subject: Re: mail/mail-notification 5.4 fails to compile
From: Marcin Wisnicki <mwisnicki+freebsd@gmail.com>
To: Torfinn Ingolfsen <tingox@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 21:13:29 -0000

It's not a workaround - it is a real fix as suggested by gconf
documentation and it's used by linux distros (see debian[1] and
gentoo[2]).

[1] http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gconf/debian/gconf2.postinst?revision=31302&view=markup
[2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/gnome2-utils.eclass?diff_format=s&revision=1.31&view=markup

On Mon, Aug 5, 2013 at 9:40 PM, Torfinn Ingolfsen <tingox@gmail.com> wrote:
> On Sun, Aug 4, 2013 at 8:42 PM, Marcin Wisnicki
> <mwisnicki+freebsd@gmail.com> wrote:
>> I guess bsd.gnome.mk should be smart enough to `killall -HUP gconfd-2`
>> at package post-install when port uses gconf (has GCONF_SCHEMAS).
>> Please file a PR against gnome ports.
>
> Are you sure that this way (killall -HUP ...) is the correct fix?
> It seems like a workaround (instead of a real fix) to me, based on the
> discussion in the two bugs I listed in my previous message.
> Also, pkill -HUP gconfd-2 didn't work for me, I had to kill the
> gconfd-2 process totally.
> HTH
> --
> Regards,
> Torfinn Ingolfsen