> If package A needs package B, and package B needs package A, why in > the world are they two separate packages?
There's rarely (if ever) a circular dependency like that. What you'll normally see is that package A needs package B, and package C needs package B. Thus package B is usually a shared component/library that is used by many other apps. They're separate packages so that: 1) the shared library can be developed independently, and 2) the app author can focus on writing the application's logic, and benefit from someone else's development of the library without having to re-invent the wheel. DR ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
