Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: adding a toplevel zsh.spec.in file
- X-seq: zsh-workers 12192
- From: Chmouel Boudjnah <chmouel@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: adding a toplevel zsh.spec.in file
- Date: 07 Jul 2000 09:15:12 -0700
- In-reply-to: Adam Spiers's message of "Fri, 7 Jul 2000 12:53:17 +0100"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <20000707125317.A1626@xxxxxxxxxxxxxxxxxxxxxxx>
Adam Spiers <adam@xxxxxxxxxx> writes:
> Hi all,
>
> I would like to add a zsh.spec.in file to the toplevel directory so
> that any tarball releases or CVS snapshots can immediately be built
> into RPMs with
>
> $ rpm -ta zsh-3.1.x-dev-y.tar.gz
>
> Are there any objections to this? If not there are a few issues to
> clear up:
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
(%makinstall is new macros of rpm-3.0.5 combined with %configure)
--
MandrakeSoft Inc http://www.mandrakesoft.com
San-Francisco, CA USA --Chmouel
Messages sorted by:
Reverse Date,
Date,
Thread,
Author