> > I had thought I would just build `gcc-2.7.2-5.deb' (I think it > > is) and then install it exactly as if it I had just downloaded it from > > the Debian-0.93 tree. > > 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. Right now I have gcc 2.6.3 from Debian 0.93, installed as a package, and gcc 2.7.2 in /usr/local/(bin|lib|...) but dpkg doesn't know about this. If I go and deinstall 2.6.3 dpkg will bark about dependencies, I guess. -Marcelo <[EMAIL PROTECTED]>
