> I see that the code is both in the (unused) preinst and in
> lilypond-data.postrm. It's actually not clear to me whether preinst or
> postrm is the best place to do this. The argument "pro" preinst is that
> one could check the old version, and only trigger the removal if we are
> upgrading an
Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-02-09 at 07:42 +0100, Frank Küster wrote:
>>
> No, it's kpsewhich. I'm looking at the script. It does not call
> mktexlsr; it does call kpsewhich, precisely to figure out the path in
> which the fonts are located, so that old files,
On Fri, 2007-02-09 at 07:42 +0100, Frank Küster wrote:
>
> > It's kpsewhich that was needed in the preinst, btw.
>
> If the TeX-related code int he preinst script was similar to the current
> postinst script, then the main tool that is called is mktexlsr.
> kpsewhich is only used before that in o
Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:
> However, the preinst in question is no longer in the package. I'm not
> sure if this is a mistake or not. I am loath to muck with it at this
> point in the release cycle.
Of course, such a change should not be made in an upload targetted at
etch.
On Thu, 2007-02-08 at 08:26 +0100, Frank Küster wrote:
> Package: lilypond-data
> Severity: normal
>
> lilypond-data declares:
>
> Pre-Depends: tetex-bin | texlive-base
>
> This seems to be wrong. First of all, a Depends should be sufficient
> unless I miss something, because the package doesn'
Package: lilypond-data
Severity: normal
lilypond-data declares:
Pre-Depends: tetex-bin | texlive-base
This seems to be wrong. First of all, a Depends should be sufficient
unless I miss something, because the package doesn't have a preinst
script at all. Second, I don't see why you need to depe
6 matches
Mail list logo
