2006/10/23, Thomas Bushnell BSG <[EMAIL PROTECTED]>:
Anders Jackson <[EMAIL PROTECTED]> writes:

> Package: lilypond-data
> Version: Should depend on tetex or texlive
> Severity: wishlist
>
> As it is now, lilypond-data PreDepends on tetex-bin, which make lilypond
> pulls in tetex.  Which is a problem if you have installed texlive instead
> of tetex.
>
> So lilypond-data should PreDepend on texlive-base-bin | tetex-bin
> (or something like this).

Why do texlive and tetex-bin conflict?

Both tetex and texlive are tex-distributions.  You only should have
one of them installed.  And tetex has no further upstream support,
what I have learned.  Upstream tetex recommends end users to switch to
texlive, so I have done this, becouse texlive is packed in Debian.

It is not allowed for two Priority: optional packages to conflict.
Perhaps you should complain to them to get their act together and
separate the command names so that this problem goes away.

I has not that much clues on how to pack software for Debian, so I
don't doubt you on that.  But it is still a problem for me if I want
to use lilypond, which I obvious want to  ;-).

If I try to install lilypond, I looses packages latex-beamer,
latex-xcolor, pgd, texlive, texlive-base, texlive-context,
texlive-latex-base, texlive-metapost and texlive-pdfetex.  And it also
will downgrade telive-latex-recommender and texlive-pictures
Which, in all I guess, will render my TeX installation more or less
usless (without trying, becouse I'm on a rather slow Internet line).

Package texinfo suggests "tetex-bin | texlive-base" and conflicts with
"tetex-base (< 3.0)" and "tetex-bin (< 3.0)"
Maybe you could have a look at how that package texinfo solved the
transition from Debian only having one TeX-distribution tetex to now
having both tetex and livetex.
It is a problem for me, becouse I can't install lilypond without
loosing texlive.

Thomas

Yours, A Jackson


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

Reply via email to