zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: GoTaR <gotar@poczta.onet.pl>, zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PLD Linux Distribution patches
Date: Sat, 30 Aug 2003 20:27:21 +0100	[thread overview]
Message-ID: <20030830192722.EE6A1850C@pwstephenson.fsnet.co.uk> (raw)
In-Reply-To: "GoTaR"'s message of "Thu, 28 Aug 2003 21:44:06 +0200." <20030828194406.GA365@os>

GoTaR wrote:

>

Hmm, it would help a little if there was some description of what the
patches are for, and possibly the patches themselves, since they're not
all that big.  The usual convention is patches appear on the zsh-workers
list for comment.  I appreciate that there is a separate pld-linux patch
system, but not all zsh-workers will look at that.

> http://cvs.pld-linux.org/SOURCES/zsh-tinfo.patch

Searches tinfo as well as other libraries for curses stuff.

This is simple enough and I've applied it to both branches.

> http://cvs.pld-linux.org/SOURCES/zsh-no_nis.patch

This appears to remove all specific NIS and NIS+ support
unconditionally on the basis that libraries now handle it.  While this
may well be true for a lot of modern systems, I don't think we can
simply assume it's valid everywhere.

If there's no test that can be done to see, the existing HAVE_NIS and
HAVE_NIS_PLUS tests in zshconfig.ac could be qualified so that the
macros aren't defined on systems known not to need them.  I think that
would be a simpler patch anyway.

-- 
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk


       reply	other threads:[~2003-08-30 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030828194406.GA365@os>
2003-08-30 19:27 ` Peter Stephenson [this message]
2003-11-19 19:28 ` Clint Adams
     [not found]   ` <20031207143451.GA9608@os>
2003-12-07 15:09     ` Clint Adams

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=20030830192722.EE6A1850C@pwstephenson.fsnet.co.uk \
    --to=pws@pwstephenson.fsnet.co.uk \
    --cc=gotar@poczta.onet.pl \
    --cc=zsh-workers@sunsite.dk \
    /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).