unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 56222@debbugs.gnu.org
Subject: bug#56222: Emacs 28.1 distribution tarball does not unpack on Solaris 10
Date: Sun, 26 Jun 2022 21:37:01 +0300	[thread overview]
Message-ID: <83r13b8e5u.fsf@gnu.org> (raw)
In-Reply-To: <6c8a14e5-6ff0-44d1-7df8-8ffe4c042d19@cs.ucla.edu> (message from Paul Eggert on Sun, 26 Jun 2022 13:10:58 -0500)

> Date: Sun, 26 Jun 2022 13:10:58 -0500
> Cc: 56222@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 
> On 6/26/22 10:19, Eli Zaretskii wrote:
> > Do I understand correctly
> > that these two problems could be worked around by installing GNU Find?
> 
> Yes, just as the tarball problem can be worked around by installing 
> Solaris 10's optional GNU tar package.

Being unable to unpack a tarball is much worse that being unable to
run the test suite or clean the build tree, though.  I'm sure some
people won't even know how to proceed in that situation.

> In short although GNU findutils is doable, it's a hassle that is better 
> avoided.

I'm reluctant to make changes in the build scripts on the release
branch at this point.  make-dist only affects Emacs maintainers who
prepare the tarball, so having some trouble there is not a
catastrophe.  But a problem in Makefile's will affect everyone who
builds the release.  So I'd prefer to keep those two changes on master
for now.





  reply	other threads:[~2022-06-26 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 20:40 bug#56222: Emacs 28.1 distribution tarball does not unpack on Solaris 10 Paul Eggert
2022-06-26 13:24 ` Eli Zaretskii
2022-06-26 15:13   ` Paul Eggert
2022-06-26 15:19     ` Eli Zaretskii
2022-06-26 18:10       ` Paul Eggert
2022-06-26 18:37         ` Eli Zaretskii [this message]
2022-06-26 22:46           ` Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r13b8e5u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56222@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).