all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 13984-done@debbugs.gnu.org, Kenichi Handa <handa@m17n.org>
Subject: bug#13984: Automate the build of ja-dic.el
Date: Sun, 17 Mar 2013 21:46:01 -0700	[thread overview]
Message-ID: <51469C09.6080600@cs.ucla.edu> (raw)
In-Reply-To: <jwvhakabvq5.fsf-monnier+emacs@gnu.org>

On 03/16/2013 07:36 PM, Stefan Monnier wrote:

> By "bootstrap builds" you mean "builds from the Bzr repository". 

Yes, thanks, I fixed that in the commentary.

> the problem I see with your patch (whose goal I agree with) is that
> it adds a dependency on Awk, which is probably going to be a problem for
> the Windows contributors.

That shouldn't be a showstopper, as Awk ports are widely available
for Windows, and the GNU coding standards have said for many years
that it's OK to assume Awk.  For this particular case, though,
it's easy to remove the dependency on Awk so I did that.

On 03/16/2013 08:55 PM, Eli Zaretskii wrote:

> Another problem is with the file name SKK-JISYO.L.unannotated,
> since it clashes with SKK-JISYO.L on 8+3 DOS filesystems.  Can we use
> a different name, please?

I altered things so that the file is not needed, which sidesteps
the problem.  I agree with Andreas that we should come up with a better
way of dealing with the 8+3 problem, though, so as to be less intrusive
to mainline development.

Installed as trunk bzr 112072 and marking this bug as done.





  parent reply	other threads:[~2013-03-18  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16  6:13 bug#13984: Automate the build of ja-dic.el Paul Eggert
2013-03-17  2:36 ` Stefan Monnier
2013-03-17  3:55   ` Eli Zaretskii
2013-03-17  8:46     ` Andreas Schwab
2013-03-18  4:46   ` Paul Eggert [this message]
2013-03-18 13:01     ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51469C09.6080600@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=13984-done@debbugs.gnu.org \
    --cc=handa@m17n.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.