From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: adding a toplevel zsh.spec.in file
Date: Fri, 07 Jul 2000 13:45:33 +0100 [thread overview]
Message-ID: <0FXB00E50VFWXR@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Fri, 07 Jul 2000 12:53:17 BST." <20000707125317.A1626@thelonious.new.ox.ac.uk>
> 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:
>
> - Do we also bundle a zsh.spec in releases? I vote yes, otherwise
> the whole exercise is a bit pointless.
That won't be a problem. Just add it to .distfiles.
> - Should zsh.spec be included in the CVS tree? Yes goes against the
> grain, since all other auto-generated files aren't, but no means
> that CVS snapshots can't be built immediately as above.
It's not worth it; you can't bundle a raw CVS tree anyway, you have to run
preconfig. Get that to do any pre-configuation stuff.
> - I would like to include some sample startup files for a typical
> RedHat box. I already have these - taken from an official RedHat
> zsh rpm, and then much improved (mainly through suggestions from
> Bart). Would it be OK to add these in a new StartupFiles/RedHat
> directory? Or is it time that the current StartupFiles files
> (written for 2.7) got a rehaul anyway?
It's ancient, it really should be completely rewritten and preferably
divided up into indiviual files doing different things, with any compctl
stuff stuck in a subdirectory for legacy code.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-07-07 12:46 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 [this message]
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56 ` Adam Spiers
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=0FXB00E50VFWXR@la-la.cambridgesiliconradio.com \
--to=pws@cambridgesiliconradio.com \
--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).