Re: Packaging "feynmf" LaTeX macros: some questions about new TeX policy
On Thu, Nov 17, 2005 at 15:29 -0500, Kevin B. McCarty wrote:
> I've packaged feynmf (ITP bug #339513), a set of LaTeX macros that use
That's nice, since feynmf is one of the packages I always had to add to
my teTeX system.
> Metafont to create Feynman diagrams. (For those who aren't physicists,
Or MetaPost, which I think is more useful nowadays. I think it would be
good to mention MetaPost in the package description.
> Feynman diagrams are schematic illustrations that show how subatomic
^^^^^^^^^^^^^^^^^^^^^^^
That's a bit of an understatement. ;-)
> Note: the source on CTAN is only available in a .zip file so I had to
> repackage the orig.tar.gz :-(
Annoying, indeed.
> 1) How to ensure it's compatible and installable with both TeX Live and
> teTeX?
TeX Live includes feynmf in texlive-metapost, so Norbert would have to
remove feynmf from that package first. I don't know which TeX Live
packages should be used as dependencies. Maybe texlive-latex and/or
texlive-basicbin. Otherwise there should be no problems with
compatibility.
> 2) Depending on the right version of the TeX directory structure? I've
> arranged the .deb so it conforms to version 1.1 (please double-check
> this). Right now I only Depend upon "tetex-bin (>= 3.0-9)", since
> that's the first version of teTeX whose Debian changelog entry says it
> follows version 1.1 of the TDS. Should I depend on tex-common instead,
> and if so, which version?
Your package includes no files that have changed their location in TDS
1.1 as compared to TDS 1.0. Therefore, it should even work with teTeX 2
or teTeX 1, so that I think it should be enough to Depend on tetex-bin
without version number.
> 3) What to do in the postinst/postrm scripts? Right now I just run
> mktexlsr in both cases (checking to make sure it exists in the postrm).
> The example maintainer scripts in the Debian TeX policy appear to be
> for font packages so they don't help me too much.
Yes, these are for font packages, which are much more complicated. But
one can still use them as example, which is why I would use
if which mktexlsr >/dev/null; then mktexlsr; fi
on configure|abort-upgrade|abort-remove|abort-deconfigure in postinst
and on remove|disappear in postrm.
BTW, it is good that you rename the documentation (one of the
'manual.ps' cases) and make it available to texdoc.
cheerio
ralf
Reply to: