all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: IZarc problem extracting emacs-24.2.tar.xz
Date: Fri, 01 Feb 2013 21:03:23 -0500	[thread overview]
Message-ID: <jwvhalv5vn7.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: v8uboc4ronw.fsf@mailinator.com

>>> I noticed that some files were missing. For instance,
>>> .../etc/{DOC,DOC-X} were not extracted.
>> These files are not source code files or needed to build GNU Emacs so
>> they are not included in the sources archive.
> Your comment is correct and irrelevant.

It's quite relevant: those files are not part of the tarball, so it's not
a bug in IZArc that those files "are not extracted" (I still
recommend you stay away from IZArc, since it is proprietary software).
You can use djtarnt among many other Free Software alternatives.

> Those files are needed when using Emacs;

And they're created from the content of the tarball.

> and few users of Emacs on Windows will want to build Emacs anyway.

But I expect that most/all those who download and extract
emacs-24.2.tar.xz will want to build Emacs, since there's not much else
they can do with it.

> There is something quite wrong with IZArc.

Indeed: it is proprietary.


        Stefan


  reply	other threads:[~2013-02-02  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 20:34 IZarc problem extracting emacs-24.2.tar.xz Bug Dout
2013-01-28 21:12 ` Peter Dyballa
     [not found] ` <mailman.18502.1359407692.855.help-gnu-emacs@gnu.org>
2013-02-01 16:20   ` Bug Dout
2013-02-02  2:03     ` Stefan Monnier [this message]
2013-02-02  8:18       ` Eli Zaretskii
     [not found]       ` <mailman.18836.1359793101.855.help-gnu-emacs@gnu.org>
2013-02-20  1:43         ` David Combs
2013-02-20 18:40           ` Eli Zaretskii

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=jwvhalv5vn7.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.