zsyncmake(1)

📦
version 0.6.6 · 4 versions
, in arch rolling

🦋 zsyncmake(1) — Build control file for zsync(1) 🦋

okay so bestie, welcome to the zsyncmake manual page (that's the zsyncmake(1) situation, file transfer vibes only) 💅

✨ NAME ✨

zsyncmake — build the control file for zsync(1) 🎀

🌸 SYNTAX 🌸

blocksize ] [ -o outfile ] [ -f targetfilename ] [ -v ] filename

zsync -V

💖 DESCRIPTION 💖

So what this icon does is construct a metafile — literally a file about a file — that the zsync client program uses to do partial file downloads. filename is the file that users wish to downloads (yes that's the manpage's grammar, we keep it, we love it 💀); zsyncmake constructs the appropriate metafile and writes filename.zsync in the current directory. no cap, that's it.

zsync will need at least one URL from which to download the file content. If the .zsync will be in the same directory as the file to download, you can just accept the default — zsync includes a relative URL in the control file. cute, right? 🫶 But if it's not in the same directory, use the -u option to specify the URL. You should also specify a URL for the uncompressed content with -U if available, because zsync can make use of this for more efficient downloads sometimes. (You can edit the .zsync file and add these afterwards — it has a simple key: value format in the header — but I suggest you only do this once you are familiar with the tool. lowkey a "trust me bestie, walk before you run" moment 🙈)

⚠️ heads up: zsyncmake itself does not (currently) verify the URLs or download any data. You must provide the file data locally and check the URLs yourself. she is not doing that labor for you, bestie 😭

💅 OPTIONS 💅

  • -b blocksize — specify the blocksize for the underlying rsync algorithm. A smaller blocksize may be more efficient for files where there are likely to be lots of small, scattered changes between downloads; a larger blocksize is more efficient for files with fewer or less scattered changes. This blocksize must be a power of two. If not specified, zsyncmake chooses one which it thinks is best for this file (currently either 2048 or 4096 depending on file size) — so normally you should not need to override the default. she's got this ✨
  • -C — DEPRECATED. Tells zsyncmake not to generate any instructions in the .zsync telling the client to compress the data it receives. This is implied by -z, but this option is here in case you compress a file yourself only for the transfer, but want the client to end up with the uncompressed file (e.g. you are transferring an ISO, which is held compressed on the server, but which the client cannot use unless it is uncompressed). Without -C, zsyncmake will produce directions for the client to compress the file it receives where appropriate; -C is here so you can stop it telling the client to do that. 💅
  • -e — DEPRECATED — this is only useful for compressed files without -Z specified; support for this case will be removed in a future verson (yes, "verson", we're keeping the typo, it's canon now 😭). Tells zsyncmake that the client must be able to receive the exact file that was supplied. Without this option, zsyncmake only gives a weaker guarantee — that the client will receive the data it contains (e.g. it might transfer the uncompressed version of a .gz to the client). Note that this still doesn't guarantee that the client will get it — the client could ignore the directives in the zsync file, or might be incapable of exactly reproducing the compression used. But with -e you know that zsyncmake has made it possible to get the exact data — it will exit with an error if it cannot. so it's giving "best effort, but make it loud" 🫡
  • -f filename — set the filename to include in the output file (this is what the file will be called when a user finished downloading it). naming rights, iconic 👑
  • -o outputfile — override the default output file name. she can be called whatever you want, main character energy 🌈
  • -u url — specifies the URL from which users can download the content of the supplied file. Users need the control file in order to find out what parts of the file they already have, and they need the URLs to retrieve the parts of the file that they don't already have. You can specify multiple URLs by specifying -u multiple times. If not specified, zsync assumes that the file and the .zsync will reside in the same public directory, and includes a single relative URL. stack 'em up, the more the merrier fr fr 🍓
  • -U url — DEPRECATED. Specifies a URL corresponding to the decompressed content of the file (only applicable if it is a gzip file). zsync can sometimes download more efficiently from the uncompressed data than from the compressed data — it will take advantage of this if available. If no URLs are specifies (another typo, keeping her 🎀), zsync looks for a file without the .gz extension and assumes that this will be in the same public dir as the .zsync, and includes a relative URL to it.
  • -v — enable verbose messages. she will yap. affectionately 💬
  • -V — prints the version of zsync. vibe check on the version ✨
  • -z — DEPRECATED. Compress the file to transfer. Note that this overwrites any file called filename.gz without warning (if you don't give a filename, e.g. because you are reading from stdin, then zsync will use the name supplied with -f, or as a last fallback, zsync-target.gz). ⚠️ like, it will genuinely just eat that file, no questions asked, you have been warned bestie 💀
🧚 so zsync can work with compressed data, and, in most cases where the data is not already compressed, it is more efficient to compress it first. While you can just compress the file to transfer with gzip, if you use this option then zsyncmake will compress the file for you, producing a .gz file which is optimised for zsync. This can be 30% more efficient at download time than compressing with gzip --best — but the compressed file will not be as small as that produced by gzip. trade-offs, bestie, trade-offs 😌
  • -Z — by default, zsyncmake looks inside gzip compressed files and exports the underlying, uncompressed data to the zsyncmake file. -Z disabled this, causing zsync to treat the gzip file like any other file and merely generate a download for the raw compressed data. This setting is recommended to be used for files compressed with --rsyncable. noted and slayed 🫶

🔥 EXAMPLES 🔥

http://ftp.uk.debian.org/debian/dists/sarge/main/binary-i386/Packages.gz
Packages.gz

note use of -C to save the client compressing the file on receipt; the Debian package system uses the file uncompressed. king behavior 👑

http://www.mirrorservice.org/sites/ftp.freebsd.org/pub/FreeBSD/ports/distfiles/zsync-0.2.2.tar.gz
zsync-0.2.2.tar.gz

This creates a zsync referring to the named source tarball, which the client should download from the given URL. This example is for downloading a source tarball for a FreeBSD port, hence -e is specified so the client will be able to match its md5sum. chef's kiss, checksum supplied 🤌

👑 AUTHORS 👑

Colin Phipps <cph@moria.org.uk> — the icon, the legend ⭐

🌈 SEE ALSO 🌈

zsync(1) — go read the client side too, iykyk 💜

okay that's the whole page bestie, go forth and make control files 💖

sign-off: this gem is zsyncmake(1) from version 0.6.6, brought to you by Colin Phipps, and she's out here living her best File Transfer life. periodt. 🎀🦋✨

📦 where this page comes from