From: jari <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: Re: missing 64bit ports (xdelta3 vs xdelta and pristine-tar)
Date: Fri, 17 Jul 2015 07:22:00 -0000 [thread overview]
Message-ID: <20150717072234.GJ26914@picasso.cante.net> (raw)
In-Reply-To: <55A89361.3000802@gmail.com>
On 2015-07-17 07:32, Marco Atzeri wrote:
| On 7/17/2015 1:52 AM, jari wrote:
| >
| >There will be need for pristine-tar for long foreseeable future. It's
| >mature already.
| >
| >| The option above may no longer be needed with xdelta3, since from
| >| reading the manpage it seems it no longer automatically decompresses
| >| its input. But there are likely other incompatibilities.
| >
| >Let's hear what the xdelta3 developer says about xdelta1 --pristine
| >option. I can then patch the code and test it more.
| >
| >Jari
| >
|
| his answer:
|
| "Xdelta3 and xdelta1 use completely different file formats. I have
| considered an option to translate old xdelta1 patchfiles into current
| xdelta3 patchfiles, but bugfixes and release work keep taking priority."
|
| I will repack xdelta1
|
| As I already bumped xdelta to 3.x series
| any problem if I create a new xdelta1 package ?
All good, provided that:
xdelta1 => /usr/bin/xdelta (the original)
xdelta3 => /usr/bin/xdelta3
Jari
next prev parent reply other threads:[~2015-07-17 7:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:24 missing 64bit ports Marco Atzeri
2015-07-15 17:39 ` Marcos Vives Del Sol
2015-07-15 17:48 ` Warren Young
2015-09-26 9:51 ` Marco Atzeri
[not found] ` <CABKfh3ywLyGB1gAkjwTFv0HXQc+kp4SiRHFu1ymWj=Qn4_hxcw@mail.gmail.com>
2015-09-28 7:24 ` Marco Atzeri
2015-07-15 17:47 ` Warren Young
2015-07-15 18:28 ` Corinna Vinschen
2015-07-15 19:32 ` Warren Young
2015-07-15 20:12 ` Ken Brown
2015-07-16 8:07 ` jari
2015-07-16 8:10 ` Marco Atzeri
2015-07-16 8:17 ` missing 64bit ports (xdelta3 vs xdelta and pristine-tar) jari
2015-07-16 18:35 ` Achim Gratz
2015-07-16 18:43 ` Marco Atzeri
2015-07-16 23:52 ` jari
2015-07-17 5:32 ` Marco Atzeri
2015-07-17 7:22 ` jari [this message]
2015-07-17 8:22 ` Marco Atzeri
2015-07-17 18:17 ` Achim Gratz
2015-07-18 8:11 ` jari
2015-07-18 19:00 ` Achim Gratz
2015-07-18 19:46 ` Marco Atzeri
2015-07-19 11:05 ` jari
2015-07-19 14:47 ` Marco Atzeri
2015-07-17 7:32 ` missing 64bit ports Corinna Vinschen
2015-07-17 8:39 ` Marco Atzeri
2015-07-17 9:50 ` Corinna Vinschen
2015-07-17 9:59 ` Marco Atzeri
2015-07-19 5:40 ` Marco Atzeri
2015-07-19 7:05 ` Corinna Vinschen
2015-07-19 7:18 ` Marco Atzeri
2015-07-19 8:46 ` Corinna Vinschen
2015-07-19 11:02 ` jari
2015-07-20 7:29 ` Corinna Vinschen
2015-09-03 13:58 ` Marco Atzeri
2015-09-27 15:09 ` Marco Atzeri
2015-07-17 12:53 ` Ken Brown
2015-07-17 16:35 ` Marco Atzeri
2015-07-16 8:18 ` missing 64bit ports (edit Gdocs problem) jari
2015-07-16 9:25 ` Marco Atzeri
2015-07-20 18:17 ` missing 64bit ports Jon TURNEY
2015-07-20 19:00 ` Corinna Vinschen
2015-07-22 9:08 ` Marco Atzeri
2015-09-03 13:55 ` Marco Atzeri
2015-09-03 15:45 ` Corinna Vinschen
2015-09-04 13:56 ` Jon TURNEY
2015-09-04 14:03 ` Corinna Vinschen
2015-09-07 14:01 ` Jon TURNEY
2015-09-07 15:11 ` Corinna Vinschen
2015-09-17 17:19 ` Yaakov Selkowitz
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=20150717072234.GJ26914@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).