zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: MACHINES, FEATURES, etc.
Date: Wed, 30 May 2018 14:26:16 +0100	[thread overview]
Message-ID: <20180530132618eucas1p25b292ba9c0eba4e6859ae67579fc24b8~zbwf_04SQ1092910929eucas1p2L@eucas1p2.samsung.com> (raw)
In-Reply-To: <20180529093455.6e884257@camnpupstephen.cam.scsc.local>

On Tue, 29 May 2018 09:34:55 +0100
Peter Stephenson <p.stephenson@samsung.com> wrote:
> MACHINES is never going to be complete, because we're relying on
> reports of problems from the field, but it is intended to be accurate
> and useful, which it isn't at the moment.  It could probably be
> truncated to a note saying it's a placeholder for reports of issues
> in installation that need to be worked around --- which do get
> reported now and then --- and a request for updates.

Here's a possible short version --- I've included the entire file.
It's largely to encourage people to report problems they find
(though usually configuration problems we find out about tend
to get fixed).  I'm assuming the OS-specific information that was there
is too ancient to be of any use.

I deleted a paragraph about upgrading gcc with the OS as it's irrelevant
if gcc comes with the distribution and the days of needing to install
gcc separately are largely numbered.  I also changed the set of machines
I think are "reasonably well covered" nowadays.

pws


-----------------------------
ZSH ON SPECIFIC ARCHITECTURES
-----------------------------

This file is to record difficulties in compiling and installing zsh on
specific architectures.

The information in this list may be out of date, as the developers do
not have access to all machines.  In general, GNU/Linux distributions
and BSD derivatives including MacOS are reasonably well covered.

At the time of writing zsh is believed to comiple on all up-to-date
Unix-like operating systems.  Please let us know of any exceptions.

The intended format of entries is thus:

	Vendor: OS & version (hardware type) [zsh version tried]
		information


  parent reply	other threads:[~2018-05-30 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180527065011epcas4p11a700ef0b52cf84d167ed3a02b5560d8@epcas4p1.samsung.com>
2018-05-27  6:49 ` Eitan Adler
2018-05-29  8:34   ` Peter Stephenson
     [not found]   ` <20180529093455.6e884257@camnpupstephen.cam.scsc.local>
2018-05-30 13:26     ` Peter Stephenson [this message]
2018-05-30 13:45       ` Vin Shelton
2018-05-30 13:52         ` Peter Stephenson
2018-06-01  6:14           ` Eitan Adler

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='20180530132618eucas1p25b292ba9c0eba4e6859ae67579fc24b8~zbwf_04SQ1092910929eucas1p2L@eucas1p2.samsung.com' \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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).