zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Stemen <vince.lists@hightek.org>
To: zsh-workers@zsh.org
Subject: Re: Installation fails because the documentation is not building
Date: Mon, 21 Feb 2011 18:18:01 -0600	[thread overview]
Message-ID: <20110222001801.GA19390@quark.hightek.org> (raw)
In-Reply-To: <AANLkTin6ZDDw0R=JryDQSOy4+GOdndEQ58+VVDFeMouM@mail.gmail.com>

On Sun, Feb 20, 2011 at 09:55:51PM -0800, Wayne Davison wrote:
> On Sun, Feb 20, 2011 at 7:14 PM, Vincent Stemen <vince.lists@hightek.org>wrote:
> 
> > I assume it is failing on the "test -s" statement, because when I look in
> > the
> > Doc directory, all the man files ending in ".1" are zero length.
> >
> 
> The Doc Makefile will create 0-length *.1 files if it doesn't think that
> yodl is around. Perhaps you ran make before yodl was installed, and didn't
> remove those files?  It looks like only a "make realclean"  will remove the
> *.1 files (and you'd probably want to just manually remove the *.1 files
> instead of going to that extreme).
> 
> I'm not sure why none of the lesser clean targets will clean up the *.1
> files, though.  Maybe it is to help folks who don't have yodl installed and
> get the *.1 files manually?
> 
> ..wayne..

Ah.  Yes, that was the problem.  Manually removing them worked.  Thanks.  

Yes, I did build from the repo source prior to installing yodl for
testing the sh compatibility patches.  

Seems to me that the installation code could use some improvement here.
The build was successful without yodl but the installation was not,
which was not really a surprise.  However, after installing yodl, the
installation still failed.  Even after doing a make clean or make
distclean, and reconfiguring.  That's not a very intuitive behavior.  

If those empty files are going to be created, I would suggest, when it
checks if they are empty, if yodl is installed, then automatically
delete and re-build them.  

You might also consider, if yodl is not installed, rather than exiting
with an error, perhaps printing a message to stderr that they are being
skipped and why, then continuing without error.  If you prefer it to
exit with an error by default in this case, then perhaps print a message
providing an alternate installation target that can be used to install
without the man pages.

Vince


      parent reply	other threads:[~2011-02-22  0:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  3:14 Vincent Stemen
2011-02-21  5:55 ` Wayne Davison
2011-02-21  6:27   ` Mikael Magnusson
2011-02-22  0:18   ` Vincent Stemen [this message]

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=20110222001801.GA19390@quark.hightek.org \
    --to=vince.lists@hightek.org \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).