From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: ITP: makeself -- Utility to generate self-extractable archives
Date: Sun, 07 Oct 2012 18:26:00 -0000 [thread overview]
Message-ID: <877gr2gmvb.fsf@picasso.cante.net> (raw)
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin/makeself/makeself-2.1.5-1-src.tar.bz2 \
http://cante.net/~jaalto/tmp/cygwin/makeself/makeself-2.1.5-1.tar.bz2 \
http://cante.net/~jaalto/tmp/cygwin/makeself/setup.hint
# To check packaging
cd makeself
tar -xf *-src.tar.bz2
./*.sh --color --verbose all
Included in Debian:
http://packages.debian.org/makeself
Jari
[ setup.hint ]
sdesc: "Utility to generate self-extractable archives"
ldesc: "A small utility to generate a self-extractable archive from a
directory. The resulting file appears as a shell script (many of those
have a .run suffix), and can be launched as is. The archive will then
uncompress itself to a temporary directory and an optional arbitrary
command will be executed (for example an installation script). This is
pretty similar to archives generated with WinZip Self-Extractor in the
Windows world. Makeself archives also include checksums for integrity
self-validation (CRC and/or MD5 checksums)."
category: Archive
requires: bzip2
next reply other threads:[~2012-10-07 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 18:26 Jari Aalto [this message]
2012-10-08 4:41 ` Steven Monai
2012-10-08 13:02 ` Jari Aalto
2012-10-09 18:49 ` David Sastre Medina
2012-10-10 4:53 ` RFU: " Jari Aalto
2012-10-10 8:51 ` Corinna Vinschen
2012-10-10 5:44 ` RFU: keychain 2.7.1-1 (ITA: new maintainer) Jari Aalto
2012-10-10 9:00 ` Corinna Vinschen
2012-10-10 18:52 ` David Sastre Medina
2012-10-11 9:52 ` Corinna Vinschen
2012-10-11 16:09 ` Yaakov (Cygwin/X)
2012-10-11 16:45 ` Corinna Vinschen
2012-10-11 21:21 ` Jari Aalto
2012-10-12 13:30 ` Andrew Schulman
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=877gr2gmvb.fsf@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin-apps@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).