From: Nala Ginrut <nalaginrut@gmail.com>
To: Jason Earl <jearl@notengoamigos.org>
Cc: Guile User <guile-user@gnu.org>, Matt Wette <matt.wette@gmail.com>
Subject: Re: configuring guile packages [was: GNU Guile 2.9.8 Released [beta]]
Date: Thu, 9 Jan 2020 02:43:04 +0800 [thread overview]
Message-ID: <CAPjoZodfCq9fO3pid7UgXos-zjQQ4YF2t3=tkazwUCkreugXTA@mail.gmail.com> (raw)
In-Reply-To: <m2d0btiz6f.fsf@notengoamigos.org>
Well, I shouldn't since autoconf should deal with it automatically. I
remember I did this just because of a workaround, at that time Guile-2.2
has issue to detect the correct version number, and I was hurry to release.
Long time ago, I forget to remove it.
Best regards
On Thu, Jan 9, 2020, 02:24 Jason Earl <jearl@notengoamigos.org> wrote:
> On Wed, Jan 08 2020, Nala Ginrut wrote:
>
> > Finally I found the problem is that I left a m4/guile.m4 in Artanis for
> > some reasons. It's solved by remove it.
> >
> > Thanks for all the helps!
> >
> > Best regards
> >
> > On Mon, Jan 6, 2020 at 2:56 PM Nala Ginrut <nalaginrut@gmail.com> wrote:
>
> I am far from an expert at Autoconf, and it is entirely possible that I
> am leading you astray by mentioning this, but the Autoconf manual
> actually covers why you might want to include an updated copy of
> guile.m4 in your package instead of removing it entirely.
>
> It even uses guile as an example.
>
> https://www.gnu.org/software/automake/manual/html_node/Local-Macros.html
>
> Long story short, if you would like Artanis to be usable on older
> versions of guile that might include the older version of the guile.m4
> file that doesn't work then including the fancier new guile.m4 file in
> your package will make Artanis potentially work without a guile upgrade.
> That's almost certainly how the guile.m4 file got in your tree in the
> first place. aclocal --install probably got ran at some point and it
> included it.
>
> In this particular case, it might not be worth it to ship a local
> version of a file that will also be included with guile. As you have
> already seen local m4 files is a bit of foot gun. They are easy to
> forget, and although there are tools that will update your development
> files automagically, you have to remember to use the tools.
>
> Plus, that way you don't have to worry about testing to see if Artanis
> actually works with old versions of guile :).
>
> Thanks for your work.
>
> Jason Earl
>
next prev parent reply other threads:[~2020-01-08 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 13:36 GNU Guile 2.9.8 Released [beta] Andy Wingo
2020-01-03 5:34 ` Nala Ginrut
2020-01-03 9:02 ` tomas
2020-01-03 14:29 ` Matt Wette
2020-01-03 14:53 ` Matt Wette
2020-01-03 18:44 ` configuring guile packages [was: GNU Guile 2.9.8 Released [beta]] Matt Wette
2020-01-03 23:29 ` Matt Wette
2020-01-06 6:56 ` Nala Ginrut
2020-01-08 14:21 ` Nala Ginrut
2020-01-08 18:24 ` Jason Earl
2020-01-08 18:43 ` Nala Ginrut [this message]
2020-01-05 10:41 ` GNU Guile 2.9.8 Released [beta] Andy Wingo
2020-01-07 20:00 ` Stefan Israelsson Tampe
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='CAPjoZodfCq9fO3pid7UgXos-zjQQ4YF2t3=tkazwUCkreugXTA@mail.gmail.com' \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=jearl@notengoamigos.org \
--cc=matt.wette@gmail.com \
/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).