Bug#357983: tetex-bin: mktexmf can't write new .mf files
Florent Rougon <f.rougon@free.fr> wrote:
> Frank Küster <frank@debian.org> wrote:
>
>>> NEWS.Debian?
>>
>> Or/and a debconf question of higher priority?
>
> Well, a debconf note looks to me as a workaround for people who don't
> have apt-listchanges installed (due to ignorance), since this is purely
> informational---no user input needed. But that would also work...
Previously, you wrote:
> If I understand you correctly, Frank, you are proposing to give the
> current setup to fresh installations and have the stuff world-writable
> for those continuously upgrading, right? That would be a way to reduce
> complaints, for sure...
You did understand me correctly, but I reconsidered. I guess people who
install a TeX system first will face the same problem, and will find
that the system just doesn't work. And apt-listchanges doesn't display
NEWS files for packages that were never installed. Furthermore, upon
upgrade from sarge (without tex-common) to etch, tex-common's NEWS file
won't be displayed.
Therefore I think a debconf not is the only way to address everybody we
want to. We can still copy the content to NEWS, or keep it in README.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
Reply to: