From: Bruno Haible <bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org>
To: bug-gettext-mXXj517/zsQ@public.gmane.org
Cc: guile-devel-mXXj517/zsQ@public.gmane.org
Subject: Re: Libgettextpo wrapper for Guile
Date: Sun, 05 May 2019 15:45:18 +0200 [thread overview]
Message-ID: <16567687.pgqOOCO6U5@omega> (raw)
In-Reply-To: <20190505004925.24e650e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Miguel,
> I implemented a wrapper library
> for Guile and a couple of higher level functions, tests and I'm
> documenting everything.
This is great. Many thanks for this contribution!!
> I'd like to contribute it to GNU---a wrapper of a GNU library in the
> official GNU extension language, I think it's sensible---, but I would
> like to ask you where it would fit better:
>
> - In GNU gettext as part of gettext-tools? It could cause
> problems in the Guile bootstrap, as several tools from there
> are needed when NLS is enabled. Nevertheless, it seems to be
> the better fit in terms of code locality and cross
> maintenance.
Very good question. I think there are two aspects:
- Development aspects. Does your guile wrapper need more know-how
from the guile world or from the gettext world? (*) Will it need
regular changes as guile evolves? Surely it will need changes
when gettext-po.h evolves, but gettext-po.h has been stable
since 2010.
(*) This is relevant, because when at some point in time you
will not want to maintain it any more, will it be more easy to
find a new maintainer for it among the camp of guile developers
or among the gettext developers?
- Distributions aspects. Distros will likely package it in a
package different from gettext and different from guile, since
both gettext and guile can be used without the wrapper library.
Right?
But distros are already used to create multiple binary packages
from a single source package.
> - In Guile as an ice-9 module? As readline, it could be a
> GPLv3+ library, but also available from scratch. From my
> point of view, it would be a great option in terms of
> (zero) increment of dependencies and tight integration with
> the language.
I don't know what an ice-9 module is. I also don't know whether you
can define an ice-9 module outside of the guile package.
> - As an external library?
Would you want to have a project infrastructure with mailing list,
bug trackers, etc. for this wrapper library? I would think this is
overkill.
Bruno
next prev parent reply other threads:[~2019-05-05 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 22:49 Libgettextpo wrapper for Guile Miguel
[not found] ` <20190505004925.24e650e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-05 13:45 ` Bruno Haible [this message]
2019-05-05 16:34 ` Miguel
2019-05-05 18:45 ` Bruno Haible
2019-05-05 23:04 ` amirouche
2019-05-08 14:33 ` Miguel
2019-05-08 14:32 ` Miguel
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=16567687.pgqOOCO6U5@omega \
--to=bruno-nwnvuoht2mvytjvyw6ydsg@public.gmane.org \
--cc=bug-gettext-mXXj517/zsQ@public.gmane.org \
--cc=guile-devel-mXXj517/zsQ@public.gmane.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).