public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Eric Blake (cygwin)" <eblake@redhat.com>
To: cygwin-announce@cygwin.com
Subject: Updated: sharutils-4.15.2-1
Date: Tue, 02 Jun 2015 04:24:00 -0000	[thread overview]
Message-ID: <556D2F91.5040901@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2629 bytes --]

A new release of sharutils, 4.15.2-1, has been uploaded and will soon be
available at your favorite mirror.  This leaves 4.15-1 as the previous
build.

NEWS:
=====
This is a new upstream release.

Using shar on text mounts continues to have the possibility that line
endings on text files might not be handled the way you want, but if it
was truly a text file, that should not matter to you; the heuristic that
shar uses to decide between text and binary files is whether it contains
non-printing characters.  It is safer to use shar/unshar on binary
mounts (remembering that unshar is inherently unsafe).  uuencode and
uudecode, on the other hand, work reliably regardless of the underlying
mount point.  See also the package documentation found in
/usr/share/doc/sharutils/.

DESCRIPTION:
============
The sharutils package contains the GNU shar utilities, a set of tools
for encoding and decoding packages of files (in binary or text format)
in a special plain text format called shell archives (shar).  This
format can be sent through e-mail (which can be problematic for regular
binary files).  The shar utility supports a wide range of capabilities
(compressing, uuencoding, splitting long files for multi-part mailings,
providing checksums), which make it very flexible at creating shar
files.  After the files have been sent, the unshar tool scans mail
messages looking for shar files.  Unshar automatically strips off mail
headers and introductory text and then unpacks the shar files.

Note that unshar is inherently unsafe by design, because it executes
arbitrary shell scripts; therefore the creation of shar archives should
be limited to situations where the receiver trusts the sender.  However,
uuencode and uudecode are useful in their own right, and are safe to use.

UPDATE:
=======
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system. Save it and run setup, answer the questions and pick up
'sharutils' from the 'Archive' category.

DOWNLOAD:
=========
Note that downloads from cygwin.com aren't allowed due to bandwidth
limitations.  This means that you will need to find a mirror which has
this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html

QUESTIONS:
==========
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

-- 
Eric Blake
volunteer cygwin sharutils package maintainer

For more details on this list (including unsubscription), see:
http://sourceware.org/lists.html



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

                 reply	other threads:[~2015-06-02  4:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=556D2F91.5040901@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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.
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).