From: Andy Wingo <wingo@pobox.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: ongoing NEWS
Date: Sat, 20 Jun 2009 13:10:28 +0200 [thread overview]
Message-ID: <m3skhv6tzv.fsf@pobox.com> (raw)
In-Reply-To: <87prd1i55l.fsf@delenn.lan> (Andreas Rottmann's message of "Thu, 18 Jun 2009 23:49:26 +0200")
On Thu 18 Jun 2009 23:49, Andreas Rottmann <a.rottmann@gmx.at> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> Autocompiled files will be stored in the user's ~/.guile-ccache
>> directory, which will be created if needed. This is analogous to
>> ccache's behavior for C files.
>>
> As long as nothing is set in stone, perhaps you want to consider
> following the XDG basedir spec[0], which would suggest using something
> under ~/.cache/ per default; this would make e.g. having reasonable
> backup policies easier, as stuff under ~/.cache can be safely ignored
> for backups, and it avoids cluttering $HOME with yet-another
> dotfile/dotdir (although that is somewhat of a lost cause on GNU/Linux
> anyway).
Sure, sounds like a good idea.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2009-06-20 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:14 ongoing NEWS Andy Wingo
2009-06-18 21:49 ` Andreas Rottmann
2009-06-19 17:49 ` Neil Jerram
2009-06-20 11:10 ` Andy Wingo [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3skhv6tzv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=a.rottmann@gmx.at \
--cc=guile-devel@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.
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).