Norbert Preining <[EMAIL PROTECTED]> wrote:

> On Die, 04 Sep 2007, Frank Küster wrote:
>> > Conflict is already there, replace is not necessary since the files are
>> > installed into different trees (texmf-texlive and texmf).
>> >
>> > Closing this bug.
>> 
>> Not sure that this is correct.  If we want to take it over, and make
>> sure that users of latex-svninfo get upgraded to the latest texlive
>> version of their files, shouldn't we Conflict/Replace/Provide?
>
> A provide could be handy, but replace is useless, because no files are
> replaced. But I don't have the policy at hand ...

You don't need to read it, just remember that
"Conflicts/Replaces/Provides: foo" means that the *package* is the
successor of foo, irrespective of whether it contains the same
filenames. And this is recognized by the frontends, which install the
new package.

However, I agree with Adrian an you that it doesn't make much of a
difference. 

Regards, Frakn
-- 
Frank Küster
Debian Developer (teTeX/TeXLive)

Reply via email to