zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Raúl Núñez de Arenas Coronado" <dervishd@jazzfree.com>,
	zsh-workers@sunsite.dk
Subject: Re: How about MODDIR being configure'able?
Date: Mon, 15 Oct 2001 15:33:27 +0000	[thread overview]
Message-ID: <1011015153328.ZM8149@candle.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3CE15t82J-0007k1-00=40DervishD=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_Ra=FAl_N=FA=F1ez_de_Arenas_Coronad?= =?iso-8859-1?Q?o_=3Cdervishd=40jazzfree=2Ecom=3E?= =?iso-8859-1?Q?________=22How_about_MODDIR_being_configure'able=3F=22_=28?= =?iso-8859-1?Q?Oct_15=2C__3=3A44pm=29?=

On Oct 15,  3:44pm, Raúl Núñez de Arenas Coronado wrote:
}
}     I would like to set up the MODDIR (directory where binary modules
} of ZSH reside) through 'configure', and not by defining MODDIR prior
} to compile and install using make.

MODDIR is $(libdir)/zsh/$(VERSION).  You can't change the zsh/$(VERSION)
part without breaking things, and nothing else is installed in $(libdir),
so the module path is as completely configurable as possible with

	configure --libdir=...

}     Moreover, there is a call to mktemp that should be replaced with
} a call to mkstemp in 'utils.c' for safety.

No, we've been over this before; there's even a comment in utils.c to
this effect:  zsh uses mktemp() in a safe way.  Specifically, the names
created by gettempname() are always opened with O_CREAT later, so if
they exist the open() call will fail.  Creating them with mkstemp(), on
the other hand, causes problems with redirections and NO_CLOBBER.

}     BTW, is there any place where I can get the current development
} version of ZSH for testing?

It's available at http://sourceforge.net/projects/zsh/.  Details can be
found in the file Etc/FAQ in the distribution you have; if it's not in
there, you've got a really old distribution.

(Hey, Peter, why isn't SourceForge mentioned in the META-FAQ document?)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

  reply	other threads:[~2001-10-15 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 13:44 Raúl Núñez de Arenas Coronado
2001-10-15 15:33 ` Bart Schaefer [this message]
2001-10-15 17:41   ` Clint Adams
2001-10-16  3:42     ` O_EXCL (was: How about MODDIR being configure'able?) Wayne Davison
2001-10-16  4:12       ` Clint Adams
2001-10-16 11:58   ` How about MODDIR being configure'able? Peter Stephenson
2001-10-16 18:35 Raúl Núñez de Arenas Coronado

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=1011015153328.ZM8149@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=dervishd@jazzfree.com \
    --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).