From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,RDNS_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 Received: (qmail 13025 invoked from network); 28 Mar 2020 14:03:49 -0000 Received-SPF: pass (primenet.com.au: domain of zsh.org designates 203.24.36.2 as permitted sender) receiver=inbox.vuxu.org; client-ip=203.24.36.2 envelope-from= Received: from unknown (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTP; 28 Mar 2020 14:03:49 -0000 Received: (qmail 2153 invoked by alias); 28 Mar 2020 14:03:33 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24726 Received: (qmail 8822 invoked by uid 1010); 28 Mar 2020 14:03:33 -0000 X-Qmail-Scanner-Diagnostics: from mail-il1-f193.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.2/25758. spamassassin: 3.4.2. Clear:RC:0(209.85.166.193):SA:0(-2.0/5.0):. Processed in 3.334271 secs); 28 Mar 2020 14:03:33 -0000 X-Envelope-From: roman.perepelitsa@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.193 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Th6ILEJSgG8laA7cDwNtRwbSniOSdTvtzlvzmc4uIiA=; b=q0xrdhyCz52xd8miEWLQTNZ6SZiT+pF9UAo9ifoVYQuptPdu3NpaRxOuV8lsZhu5g9 fZwF6shZiBuBG8nybJA0HEJpV7HPFEW3bYBbaW+lASyGgllFCM0N1vPzOfGCGva+BimV NtQRD1Kmx+kZ7gSvn5vGix9y+FOmoPYeH8jx6VuNwehHz5cKOVbTlsfdST8RHi/ukckP fPjpgEdnWyZ+KS7brVk2xoZ/xWF6jBCxGCXGu7m7OxbGXP2nSLK5R4fnORcgKlR+JO7B +tfVRmbMVamrvShPg4WMoJEl8g3Jrgi76uUBboYymeooZkDMdTvGX0CLOt3KYoacf65g XN7g== X-Gm-Message-State: ANhLgQ046+HFoydrP5Ad7K6KD0vOCqR8SposaIYFg09owPE97IgYmhpT B/+DJOBucbs9EU4BmvbwW1o+93nk+p/2uAZ2SamSKFWb X-Google-Smtp-Source: ADFU+vuCq3mf6GM6TqP+5PKg3GBmRAvg92rV013k2FP+eUtE1YhaRfX1m9BP3fS+ugSjDKF9JTEFjMSpJflKWpwFQK4= X-Received: by 2002:a92:3b8c:: with SMTP id n12mr3771528ilh.186.1585404176335; Sat, 28 Mar 2020 07:02:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Roman Perepelitsa Date: Sat, 28 Mar 2020 15:02:45 +0100 Message-ID: Subject: Re: [ANN] zsh-bin: statically-linked, hermetic, relocatable zsh To: Sebastian Gniazdowski Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Sat, Mar 28, 2020 at 1:24 AM Ray Andrews wrote: > What is 'hermetic'? It means Zsh from zsh-bin doesn't require any files from outside of its installation directory to function. Perhaps "self-contained" would be a better word. > Does relocatable mean that I can just move the target directory > to anything/anywhere and so long as 'zsh' if found, all else will > work? Relocatable means you can install Zsh from zsh-bin into any directory. This isn't the case for other distributions. Usually, after Zsh is compiled, it can work only when placed in a specific directory. You can find more details in https://github.com/romkatv/zsh-bin/#how-it-works. > Which of the three methods below would be recommended? Installation with the install script is the easiest by far. It's also safer thanks to signature verification and extra care to avoid clobbering an existing installation. Manual installation is for those who like to tinker. It also serves as an explanation of what `install` does. The option to build your own archive is for those who like to tinker even more. Note that you can also use the install script to install Zsh from an archive you've built yourself. > I'm running Debian 'amd64' so which image? > I'm thinking: zsh-5.8-linux-x86_64.tar.gz That's right. The manual installation instructions show the basic algorithm for deriving the name of the archive from the OS kernel name and CPU architecture. kernel=$(uname -s | tr '[A-Z]' '[a-z]') arch=$(uname -m | tr '[A-Z]' '[a-z]') name="zsh-5.8-${kernel}-${arch}" See https://github.com/romkatv/zsh-bin#manual-installation. The install script is a bit smarter than this. Since the name of your OS kernel is Linux and CPU architecture is x86_64, zsh-5.8-linux-x86_64.tar.gz will work. > And do I understand that the whole thing will be in one subdirectory? Yes. You can simply remove this directory to "uninstall". On Sat, Mar 28, 2020 at 11:37 AM Sebastian Gniazdowski wrote: > I've ran the script and the resulting zsh seems to not support dynamic > loading at all. Indeed. I've added this limitation to the documentation: Zsh from zsh-bin cannot load user-defined compiled modules. There no way to guarantee that user-defined modules have been linked with the same libc as `zsh`, so it's unsafe to load them. This limitation likely cannot be removed. Roman.