unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] profiles: Generate GHC's package database cache.
Date: Sun, 5 Apr 2015 22:27:43 +0200	[thread overview]
Message-ID: <CAKrPhPNnYVjmqH9gq3ZvJ9bZZyDYQLW9XJ4DD6QtQMS7yExFHA@mail.gmail.com> (raw)
In-Reply-To: <87mw2mcpcj.fsf@gnu.org>

ludo@gnu.org (Ludovic Courtès) writes:

> Eventually we could think of more sophisticated way to determine whether
> to trigger a given “hook” (info-dir, ca-certificates, ghc.)  Perhaps
> this ‘ghc-package-cache-file’ procedure could be added as an
> ‘environment-hook’ field of the ghc package and it would be triggered
> iff GHC is installed.  (This approach would work well for GHC, but not
> for info-dir or ca-certificates, though.)

On top of the mentioned cases above, there are many programs making use
of caches. Some are:

* GLib's IO modules normally use a cache file 'giomodule.cache'. We set
  the env. var. GIO_EXTRA_MODULES, but it's use is explicitly
  discouraged by the project.

* XDG icons 'icon-theme.cache': I see some clashes in my profile (e.g.,
  gtk and Inkscape).

* TeX 'ls-R' files: it would probably simplify modularization.

* I see python's easy_install site.py clashes in my profile.  These are
  probably harmless, but annoying.

It would definitely be good to establish a solid and general way to run
"hooks" to address this kind of situations.

Regards,
Fede

  reply	other threads:[~2015-04-05 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 21:10 [PATCH] profiles: Generate GHC's package database cache Federico Beffa
2015-04-05  5:21 ` Mark H Weaver
2015-04-05  8:16   ` Federico Beffa
2015-04-05 20:24     ` Mark H Weaver
2015-04-05 20:33       ` Federico Beffa
2015-04-06  8:18         ` Federico Beffa
2015-04-06  8:24           ` Mark H Weaver
2015-04-06  8:27             ` Federico Beffa
2015-04-06 19:00               ` Ludovic Courtès
2015-04-10 12:30                 ` Alexandre Héaumé
2015-04-05 20:06 ` Ludovic Courtès
2015-04-05 20:27   ` Federico Beffa [this message]
2015-04-15 21:28     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKrPhPNnYVjmqH9gq3ZvJ9bZZyDYQLW9XJ4DD6QtQMS7yExFHA@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).