> > If you do that, the dependency/conflict checking performed by dpkg and > > dselect will be useless. This could lead to problems if you forget > > what you've done when you finally get around to upgrading to Debian-1.x. > > Funny, that's exactly why I want to build it as a package instead of doing > "make, make stage1, etc". I thought that by building a package I could > tell dpkg that gcc 2.7.2 is installed, so when I finally do the change to > 1.1, I can be able to deinstall this "package", and install the > replacement, debian 1.1 gcc. I guess it doesn't work like this then.
The reason this is a potential problem is that all current ELF packages assume gcc >=2.7.0 are ELF and <2.7.0 are a.out. How about this, build gcc-2.7.2-5 for a.out but change debian.control to say it's 2.6.x? This way, dpkg and other packages won't get confused. David -- David Engel Optical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
