RE: .deb dependancy hell
Whoops - my apologies, then. I didn't read your message carefully enough.
> -----Original Message-----
> From: Richard Hoskins [mailto:email@example.com]
> Sent: Wednesday, January 28, 2004 4:25 PM
> To: firstname.lastname@example.org
> Subject: Re: .deb dependancy hell
> "Rosenstrauch, David" <email@example.com> writes:
> > 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.
> It was a circular dependency that prompted my original article.
> libgphoto2-port0 depends on libgphoto2-2, and libgphoto2-2 depends on
> libgphoto2-port0. A needs B, and B needs A. You can't have A OR B.
> You need A AND B, no matter what you are using them for, or what other
> dependencies exist.
> Many people replied with ways around this, but the dependency exists,
> and is circular.
> Lift me down, so I can make the Earth tremble.
> --Bucky Katt
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact
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.