zip dependency for riscpc install archive
Are we sure that build-time dependencies on non-US programs are unacceptable?
Right now the riscpc install just doesn't work at all, which is obviously no
good. I'm not sure how to fix it yet, but I guess it needs sorting out one
way or the other in fairly short order.
------- Forwarded Message
X-Mailer: exmh version 2.3.1 01/18/2001 (debian 2.3.1-1) with nmh-1.0.4+dev
Subject: Re: cvs commit to boot-floppies by aph
In-Reply-To: Message from Debian Boot CVS Master <email@example.com>
of "Sun, 18 Nov 2001 14:33:18 PST." <[🔎] E165aV4-0005dKfirstname.lastname@example.org>
References: <[🔎] E165aV4-0005dKemail@example.com>
Content-Type: text/plain; charset=us-ascii
Date: Sun, 18 Nov 2001 23:15:37 +0000
From: Philip Blundell <firstname.lastname@example.org>
In message <[🔎] E165aV4-0005dKemail@example.com>, Debian Boot CVS Master write
>rework the way dinstall.zip is created on arm, using mini[un]zip
>rather than the zipinfo stuff, which is illegal for us to use since
>it's in non-US/main; i hope the resulting .zip actually works on
>RiscPC otherwise, uh, I think we're in a world of pain
No, it won't. :-(
The problem is that RISC OS, the RiscPC native operating system, has extra
metadata associated with each file that determines its type. This isn't
particularly important for the kernel and ramdisk images, but it's vital for
the bootloader itself. Repacking the whole archive under Linux means this
extra information will be lost and the program won't run any more.
Why's it illegal to use programs from non-US for this kind of thing? I don't
really understand why zip is in non-US in the first place, is that some kind
of patent issue?
If there's no acceptable way to build a single archive then I guess we have to
ship the kernel and root image loose, and have the bootloader in a static zip
file that doesn't get touched during build. That wouldn't be a problem to do;
it will make things a little more complicated for the user, but not unbearably
------- End of Forwarded Message