From: Thamer Al-Harbash <tmh@whitefang.com>
Cc: guile-user@gnu.org
Subject: Re: Packaging a guile-enabled binary
Date: Sun, 2 May 2004 13:52:26 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.58.0405021348110.7861@cassandra.whitefang.com> (raw)
In-Reply-To: <20040502202152.73706.qmail@web14304.mail.yahoo.com>
On Sun, 2 May 2004, Mike Gran wrote:
> 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'd drop them in /usr/local/share/program-name/foo.scm, but I'm
just following unix convention and I use the auto-tools to make
this user configurable. If your user is going to keep them in
their homedirectori then usually you can create a .prognamerc and
a direcotry .progname for files.
Can you distribute a program linked to guile in binary only? I
just checked guile-1.6.x is under the GPL and not LGPL so I don't
see how this is possible, unless you're meeting some of the other
requirements of the GPL.
--
Thamer Al-Harbash
GPG Key fingerprint: D7F3 1E3B F329 8DD5 FAE3 03B1 A663 E359 D686 AA1F
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-05-02 20:52 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 [this message]
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
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=Pine.BSF.4.58.0405021348110.7861@cassandra.whitefang.com \
--to=tmh@whitefang.com \
--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).