Archie Cobbs wrote: > You are right in that additional programs or custom modifications > that depend on the obsolete stuff would break if the obsolete stuff > were removed... so you'd have to confirm everything with mergemaster. > Possibly this is too dangerous to be useful. > > But it would be nice to get rid of those really stale header files, etc.
Yeah, that's why this discussion keeps coming up. People keep getting bit on the butt over it. 8-). You end up having to register source, target, build, and install relationships, as well as "already installed" relationships. It would really suck, too, when you had a third party package that got pulled into FreeBSD proper (e.g. first import of perl, or first import of expat2, where the built version conflicts with the installed version, but the installed version is not registered into the dependency tracking framework). It's an expensive problem to fix, and there's no way to fix it and make money from it (at least the way things stand), so there's no way to recover the expenses. Basically, you have to find someone willing to pay you to do the work, and willing to accept the risk of the code not making it back into the main FreeBSD tree because it steps on the toes of someone who could veto its inclusion. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
