From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: adding a toplevel zsh.spec.in file
Date: Mon, 17 Jul 2000 15:56:50 +0100 [thread overview]
Message-ID: <20000717155650.A6739@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <m2hfa1lxwv.fsf@cassini.us.mandrakesoft.com>; from chmouel@mandrakesoft.com on Fri, Jul 07, 2000 at 09:15:12AM -0700
Chmouel Boudjnah (chmouel@mandrakesoft.com) wrote:
> Be careful you'll have by the way need to fight with the
> RPM_BUILD_ROOT in the %install :
>
> --- zsh-3.1.9/Src/zsh.mdd.chmou Tue Jul 4 10:06:32 2000
> +++ zsh-3.1.9/Src/zsh.mdd Tue Jul 4 10:54:11 2000
> @@ -53,8 +53,10 @@
> rm -f zshpaths.h.tmp; \
> echo "\`zshpaths.h' is up to date." ; \
> else \
> + if [ ! -f .in_rpm_install ]; then \
> mv -f zshpaths.h.tmp zshpaths.h; \
> echo "Updated \`zshpaths.h'." ; \
> + fi; \
> fi
>
> bltinmods.list: modules.stamp modules-bltin xmods.conf mkbltnmlst.sh
>
> and this in %install :
>
> # Zsh hardcode the prefix in binary even at install.
> pushd Src/ && {
> touch .in_rpm_install
> %makeinstall
> } && popd
Are you sure? I've built many rpms of zsh in the past, and if you're
talking about the problem I think you are, I got around them by using
DESTDIR:
%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/usr/info $RPM_BUILD_ROOT/bin $RPM_BUILD_ROOT/etc $RPM_B
UILD_ROOT/etc/zprofile.d $RPM_BUILD_ROOT/usr/bin $RPM_BUILD_ROOT/usr/lib $RPM_BU
ILD_ROOT/usr/doc/zsh-%{version}
make DESTDIR=$RPM_BUILD_ROOT install
make DESTDIR=$RPM_BUILD_ROOT install.modules
make DESTDIR=$RPM_BUILD_ROOT install.info
next prev parent reply other threads:[~2000-07-17 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 11:53 Adam Spiers
2000-07-07 12:45 ` Peter Stephenson
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56 ` Adam Spiers [this message]
2000-07-07 17:18 ` Bart Schaefer
2000-07-07 17:44 ` Zefram
2000-07-07 18:18 ` Bart Schaefer
2000-07-17 15:09 ` Adam Spiers
2000-07-17 17:48 ` Bart Schaefer
2000-07-17 18:07 ` Adam Spiers
2000-07-17 21:05 ` Oliver Kiddle
2000-07-17 23:35 ` Adam Spiers
2000-07-18 2:32 ` Trond Eivind Glomsrød
2000-07-18 6:01 ` Bart Schaefer
2000-07-18 1:56 ` PATCH: " Zefram
2000-07-18 5:22 ` Bart Schaefer
2000-07-18 6:15 ` Wayne Davison
2000-07-18 8:31 ` How to distribute skeleton zshrc etc. (Re: PATCH: Re: adding a toplevel zsh.spec.in file) Bart Schaefer
2000-07-18 16:54 ` PATCH: Re: adding a toplevel zsh.spec.in file Trond Eivind Glomsrød
2000-07-18 6:25 ` Andrej Borsenkow
2000-07-18 9:42 ` Peter Stephenson
2000-07-18 18:22 ` Trond Eivind Glomsrød
2000-07-18 19:57 ` Zefram
2000-07-18 20:07 ` Trond Eivind Glomsrød
2000-07-18 20:37 ` Zefram
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=20000717155650.A6739@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).