On Thu, Jan 11, 2001 at 03:04:54PM +0100, Christian T. Steigies wrote:
> And if the problem does not show up I will have a working X4.0 on m68k! So I
> hope you are right... but it seems I have to do a fresh build, or is there a
> way to regenerate the makefiles from the imakefiles easily?
> I can not start that before tomorrow, building glibc2.2 now, gcc-2.95.3
> is next...
For reference: m68k is the only released architecture that doesn't have
X4 uploaded yet.
X4 can't be added to any architectures until it's ready to be added to
all architectures, because:
* Installing xfree86.dsc into testing/i386 means installing
the new xlib6g package from X4 which is binary-all.
* Install a binary-all package into any architecture in a suite
installs it into all architectures in that suite.
* Installing X4's xlib6g on m68k means everything that depends
on xlib6g is uninstallable (since xlib6g depends on xlibs which
hasn't been uploaded for m68k) which amounts to 1000 odd packages.
.
At a guess, it's probably worthwhile uploading just the X client side of
X4 for m68k, which should at least mean that if X4 is added to testing
(woody), the only thing that'll be broken is the X server, rather than
a thousand otherwise innocent packages...
At the moment, btw, all the pre-tests for xfree86 are disabled (ie, RC bugs,
how old it is, whether some of the binaries on some architectures are
out of date compared to the source).
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``Thanks to all avid pokers out there''
-- linux.conf.au, 17-20 January 2001
Attachment:
pgpMpWnbcvFsz.pgp
Description: PGP signature