From: linas@linas.org (Linas Vepstas)
Cc: guile-user@gnu.org
Subject: Re: Packaging a guile-enabled binary
Date: Mon, 3 May 2004 09:49:00 -0500 [thread overview]
Message-ID: <20040503144900.GB31268@backlot.linas.org> (raw)
In-Reply-To: <20040502202152.73706.qmail@web14304.mail.yahoo.com>
On Sun, May 02, 2004 at 01:21:52PM -0700, Mike Gran was heard to remark:
>
> Where's the best place for the Guile script? Best, in this case, means
> most foolproof for the the desktop user that is going to download the
> program as a pre-compiled package. Dot file? In the library? Is
> there a "right" way or a "standard"?
I beleive that /usr/share/your-app-name is the right place.
This is where most apps put scripts, glade files, other bits
and pieces that are cpu/arch independent (i.e. don't contain
cpu-spcific compiled bits), and don't require per-machine
changes, and are static/unchanging. This allows clever sysadmins
to NFS-mount /usr/share read-only on a bunch of clients.
Yes, theres a standard, FSSTND or something like that, the
'file system heriarchy standard', all major distros including redhat
and suse are now certified as conforming.
--linas
--
pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas@linas.org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-05-03 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 20:21 Packaging a guile-enabled binary Mike Gran
2004-05-02 20:52 ` Thamer Al-Harbash
2004-05-02 22:58 ` Mike Gran
2004-05-03 14:40 ` Linas Vepstas
2004-05-03 17:43 ` Mike Gran
2004-05-14 21:50 ` Rob Browning
2004-05-15 10:56 ` Marius Vollmer
2004-05-15 18:08 ` Rob Browning
2004-05-17 18:12 ` Marius Vollmer
2004-05-24 21:55 ` Marius Vollmer
2004-05-03 14:49 ` Linas Vepstas [this message]
2004-05-04 12:07 ` Paul Emsley
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=20040503144900.GB31268@backlot.linas.org \
--to=linas@linas.org \
--cc=guile-user@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).