Tim Phipps <[EMAIL PROTECTED]> wrote:

> Hi Peter,
> 
> On Friday 26 May 2006 14:59, Peter S Galbraith wrote:
> 
> > Tim Phipps <[EMAIL PROTECTED]> wrote:
> > > Package: xtide-data
> > > Version: 20040203-1
> > > Severity: normal
> > >
> > > There's a circular dependancy here.
> >
> > How so?
> >
> > >                                     I think xtide-data shouldn't depend
> > > on xtide. The invoke-rc.d stuff will work fine if the xtide package isn't
> > > installed.
> >
> > xtide-data only depends on xtide because it is of no real use without
> > it, 

Actually, that's not really true.  See below.

> >     not because of the invoke-rc.d stuff.
> >
> If you install xtide you get xtide-data automatically, 

Not if you use `apt-get install'.  Guess I'm old-fashioned.

>                                                        If you're using 
> aptitude or something that records this fact then if you remove xtide you 
> also remove xtide-data. Everything works with just the recommends dpend from 
> xtide to xtide-data.  If someone comes up with another program that can read 
> xtide-data they may want their program to depend on xtide-data too, ther 
> would be no need for xtide to be installed.
> 
> > Can you tell me what is the circular dependency that I'm missing?
> It's when package A depends on package B and package B depends on package A. 
> If they really do depend (i.e. break if the other isn't there then they 
> should be both put in one package.

Except package A only recommends package B.

I've now noticed that I added the dependency on xtide when the format of
xtide-data changed and was only compatible with xtide (>= 2.6-1).  I
then added:

Depends: xtide (>= 2.6-1)
Conflicts: xtide (<< 2.6-1)

I suppose the `Conflicts' can stay and the `Depends' can be removed.

-- 
Peter S. Galbraith, Debian Developer          <[EMAIL PROTECTED]>
                                 http://people.debian.org/~psg
GPG key 1024/D2A913A1 - 97CE 866F F579 96EE  6E68 8170 35FF 799E


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to