"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On Sun, Oct 01, 2000 at 02:16:44PM -0400, Adam Di Carlo wrote: > > > > boot-floppies 2.2.17 i386 is now in Incoming, and also > > <URL:http://auric.debian.org/~aph/>. > > > > We'll be building 2.2.18 hopefully within a few days, so please try > > this out quickly so we can see if it has any bad bugs.
> I built it for m68k, no problems (building). However, the changes files > lists a README.pl file (polish readme) which is m68k specific (m68k is > mentioned there). No, dude, it's just the exact same as README-Users.m4, just translated. It should be handled just the same. > Its impossible to upload this, since builds for other > arches will probably also have this file, for their special architecture. Eh? > m68k: the mac people want to bump up their kernel to 2.2.16. When we finally > receive the patches, we might be able to built 2.2.16 kernel images for the > other architectures as well, until then we would have to use 2.2.16 for mac > and 2.2.10 for everybody else, is it possible to do that for m68k (I think > Ive seen something similar for powerpc)? Sure, I think so. Just fudge around int he top-level Makefile. Are the kernels uploaded for Potato yet? > Special request: for hardware not supported by 2.2.16 it was recommended to > have a macinstallback.tgz which uses 2.2.10, is that feasable? You are wanting to make Mac install disks for 2.2.10 as well as 2.2.16? This makes my heart sink. Is that really necessary? > I think we want new kernel images (2.2.10) for amiga and atari anyway, how > much time do we have till 2.2.18 (hint for debian-68k: I need the patches to > go in, without them I can not built kernel-images)? Christian, you should feel free to burn and release point versions for Mac at any time. Just tag/dpkg-buildpackage -uc -us/debsign then upload it. It's just a source upload rather than just a binary upload. Thus we could have 2.2.18 on Tuesday (i386) then 2.2.19 on Friday (m68k) or whatever, it doesn't matter, integers are cheap and plentiful. I don't believe in making all ports wait for all other ports. -- .....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/>
