From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Brasero, or gnome without gnome Date: Thu, 3 Oct 2013 13:01:13 +0200 Message-ID: <20131003110113.GA6327@debian> References: <20131002124146.GA15506@debian> <20131002180223.GA873@debian> <874n8zsc3c.fsf@gnu.org> <20131002205600.GA1680@debian> <87a9irpbb0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50650) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRgf1-0003b6-UG for guix-devel@gnu.org; Thu, 03 Oct 2013 07:01:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VRgeu-0007sW-KV for guix-devel@gnu.org; Thu, 03 Oct 2013 07:01:35 -0400 Content-Disposition: inline In-Reply-To: <87a9irpbb0.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?iso-8859-15?Q?Court=E8s?= Cc: guix-devel@gnu.org On Thu, Oct 03, 2013 at 12:17:39AM +0200, Ludovic Courtès wrote: > Do you mean a solution that does not require any action upon > installation? That would at least require using different file names > than just ‘gschemas.compiled’, no? Yes. I also wondered if these were needed; one could imagine that this compilation step would just be a caching mechanism, and that things still work if the uncompiled original xml files are present. But this does not seem to be the case as far as I can tell from my tests - brasero insists on its xml file having been compiled into gschemas.compiled. And this is also what happens in debian. > What I had in mind is that upon installation in the user’s profile, the > glib-compile-foobar command would be run for all the schema-providing > packages to appear in the new profile. This could even be done automatically without specifying it in the package description whenever a package contains a file in share/glib-2.0/schemas/. The glib-compile-schemas (there is also glib-compile-resources) is part of the glib package, so should be available as an input to such a package. But which glib version would we choose then when constructing the user profile? Different installed packages could have different glibs as inputs, for instance. The one that is "current" in the sense that it would be installed by "guix package -i glib"? Andreas