From: "Marco Maggi" <marco.maggi-ipsu@poste.it>
To: "guile-user" <guile-user@gnu.org>
Subject: Re: modules and version numbers
Date: Sat, 13 Oct 2007 09:04:30 +0200 [thread overview]
Message-ID: <JPU8ZI$8CA93F1319F29D4BED40563B8276C0AD@poste.it> (raw)
"Andy Wingo" wrote:
>On Fri 05 Oct 2007 16:34, "Marco Maggi"
<marco.maggi-ipsu@poste.it> writes:
>> I am thinking about adding a version number to my modules;
>I documented the guile-gnome strategy here:
>
>http://www.gnu.org/software/guile-gnome/docs/tutorial/getting-started/#getting-started
Thanks, special versioned modules are tempting... If I
allow parallel installations:
${sitedir}/gee/<full-version>/...
${sitedir}/gee/<other-full-version>/...
then there are two options:
* to use GUILE_LOAD_PATH explicitly
* to load first a special module (gee <full-version>)
then in each versioned module hierarchy I can have
(modname-1) and (modname-2) to support new
and old interfaces, or simply (modname).
I think that I can set up this installation layout
along with the special modules as a "configure"
option. It makes more difficult to write Autoconf
modules to be used in downstream packages,
though.
As I understand it, even pkg-config wants versioned
meta file names on its command line; on my
system there are 3 versions of xaw installed and
their meta files are "xaw6", "xaw7" and "xaw8";
if I try "pkg-config xaw --libs" it says to go
fly my kite.
So I have to write my own file system inspection
script to find the available versions of a package.
:-(
--
Marco Maggi
"Now feel the funk blast!"
Rage Against the Machine - "Calm like a bomb"
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2007-10-13 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 7:04 Marco Maggi [this message]
2007-10-15 9:10 ` modules and version numbers Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2007-10-05 20:34 Marco Maggi
2007-10-08 7:56 ` Ludovic Courtès
2007-10-12 14:13 ` Andy Wingo
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='JPU8ZI$8CA93F1319F29D4BED40563B8276C0AD@poste.it' \
--to=marco.maggi-ipsu@poste.it \
--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).