On Sun, 2011-11-20 at 12:30 -0600, Peter Samuelson wrote: > [Goswin von Brederlow] > > Ugly, but if it works ... You only have those 2 choices for Multi-Arch: > > same: Split the package or make the files equal. > > Well, the third choice is to assume nobody _really_ cares about > multiarch for JNI libraries, and just drop the Multi-Arch: header. > > > Since you are building the jarfile somewhere in your source you could > > fix the place where it is created in the first place. But that > > probably means patching the upstream Makefile. > > The jar is created with the command 'jar cf $output -C $inputdir org' > (where 'org' is the top level of the class name). The 'jar' from > gcj-4.6, at least, packs the zip file in 'readdir' order. > > I tried repacking, but can't get zip to produce consistent output, even > on a single platform. Looks like there's one byte per stored > directory, and two bytes per stored file, that change on each 'zip' > invocation. I'm testing with zip 3.0-4 on kfreebsd-i386. By default, zip stores all timestamps including access time, which is obviously liable to change. You can suppress time and ownership information with the '-X' option. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'
Description: This is a digitally signed message part