Bug 23499

Summary: [NEW PORT]: Two LaTeX macro package ports
Product: Ports & Packages Reporter: bsdport <bsdport>
Component: Individual Port(s)Assignee: Ade Lovett <ade>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.shar none

Description bsdport 2000-12-12 11:40:02 UTC
Included below are two new ports, they are both LaTeX macro packages.

Although LaTeX packages are reasonably easy to install by hand they are
just complicated enough to benefit from the ports system.  Plus novice
users or users of LyX may find it easier to install a port/package.

Due to the similarity of these ports (and any other future ports of
LaTeX packages) I split out all the common stuff from the makefiles and
put it into Mk/bsd.latex.mk and modified Mk/bsd.port.mk to include it
when LATEX_PORTNAME is defined.  A ports god type person will probably
want to review this file.  I tried to comment it well and follow the
example of the other Mk/bsd.*.mk files.

In case the way I did Mk/bsd.latex.mk is unacceptable I also included
print/*/Makefile.standalone which are normal everyday port Makefiles for
the two ports.  Either the standalone makefiles should be renamed and
committed or the bsd.latex.mk changes should be commited, not both.

I've tested the two ports with both sets of makefiles so that they
build, install, deinstall, and build a package that installs and
deinstalls cleanly.

There are a couple of small issues that I'm not entirely happy with
however.  With "make install" I've put in a variable to control the
running of "texconfig rehash" but I didn't make a way to turn this
off in the package (it's always done via an @exec/@unexec pair in
the plists).  Similarily, if the LaTex macro package is one which
is auto-detectable by LyX then "make install" will by default run
${PREFIX}/share/lyx/configure" (if it exists), I couldn't think of a
clean way of doing this quickly in the package so I ignored it.  Neither
of these issues are very important.
Comment 1 Will Andrews freebsd_committer freebsd_triage 2001-04-07 08:12:17 UTC
State Changed
From-To: open->analyzed

I don't think having a bsd.latex.mk just for 2 ports is an awesome 
idea, unless you would like to expand the domain of bsd.latex.mk. 
Generally, Mk/bsd.*.mk should be for complicated and large groups 
of ports.
Comment 2 Ade Lovett freebsd_committer freebsd_triage 2002-04-13 04:04:02 UTC
State Changed
From-To: analyzed->closed

Timeout (1 year) in analyzed. 


Comment 3 Ade Lovett freebsd_committer freebsd_triage 2002-04-13 04:04:02 UTC
Responsible Changed
From-To: freebsd-ports->ade

My fault[tm]
Comment 4 bsdport 2002-04-13 16:04:22 UTC
BTW if anyone is still interested in this I have updated the
bsd.latex.mk file and I now have about 14 ports in my private
ports dir that use it.  I haven't bothered trying to submit
them due to the underwhelming response I got from this PR but
I could easily re-test ans submit them all in a single PR.

Also note the ddm.crosswinds.net -> ddm.wox.org address change.

Thanks.
-- 
Dave Chapeskie
OpenPGP Key ID: 0x3D2B6B34