Bug#100332: New package splitting scheme for teTeX in Debian
Ralf Stubner <ralf.stubner@web.de> wrote:
> On Thu, Oct 27, 2005 at 15:56 +0200, Frank Küster wrote:
>> >> mpost,
>> >> mpto,
>> >> makempx
>> >> /usr/bin/makempy (MetaPost)
>> >> /usr/bin/mptopdf
>> >
>> > I would suggest that MetaPost is now regarded as a core component of a
>> > modern TeX distribution, so I'd suggest keeping it in the core.
>>
>> Hm, well. So far, I have not looked at tetex-bin-core (and the new
>> tetex-base) as "core of a modern TeX distribution", but rather as "what
>> is needed in a Build-Depends". From this point of view I doubt that
>> MetaPost has its place in -core. What do others think?
>
> I am a regular MetaPost user, but I would vote for it going to
> tetex-bin-extra. The TEXMF/metapost directory allready is in tetex-extra
> and should stay there. I don't expect anybody to uses it for a
> Build-Depends. One could try to find out what all the packages
> build-depending on tetex-extra actually use, but that would be a lot of
> work.
Unrelated to MetaPost, or at least not specific: Once the newly split
packages are in unstable, I suggest we send a mail to devel-announce
and/or all packages (build-)depending on tetex-extra and ask people to
check whether they still need this. We also ask them to tell us if they
do, and if we have a lot of time we can even do a mass bug filing on
packages that depend on -extra but have not told us that they still need
to.
>> >> /usr/bin/allcm
>> >> /usr/bin/allec
>> >> /usr/bin/allneeded (create many CM/EC pk fonts at once)
>> >
>> > Why throw away these scripts?
>>
>> In order to keep tetex-bin-core as small as possible. Not because of
>> disk space, but in order to keep it simply. I don't think that any sane
>> mind will call allcm in debian/rules before running latex over their
>> documentation. Am I insane myself?
>
> These scripts are useful when one installs a system and does not wnat to
> wait for font creation when 'in production use'. It would be pointless
> and counterproductive to call them from debian/rules, since more fonts
> than necessary would be created.
Of course - the question was rethorical. So the answer to Julian's
question is: Because they are not needed on build-depending packages.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: