Hello,
Looking for a lightweight PDF viewer I stumbled upon mupdf, which
seems to do most of the things I want. I therefore started to look at
packaging it for Fink. My attempt looks like this:
---------- mupdf.info begins ----------
Package: mupdf
Version: 1.6
Revision: 1
Depends: <<
x11
<<
BuildDepends: <<
fink (>= 0.28),
x11-dev
<<
Source: http://www.mupdf.com/downloads/%n-%v-source.tar.gz
Source-MD5: 8d69db41ae9e0b6807b76bb6ed70dc2f
License: GPL
PatchScript: <<
sed -i~ -e 's,/usr/local,%p,' Makefile
<<
CompileScript: <<
make
<<
InstallScript: <<
make install DESTDIR=%d
cd %d/sw/bin && ln -s mupdf-x11 mupdf
<<
DocFiles: CHANGES CONTRIBUTORS COPYING README
DescPackaging: <<
TODO: Find dependencies (if any)!
<<
Description: Lightweight PDF viewer
Maintainer: Stefan Bruda <f...@bruda.ca>
Homepage: http://www.mupdf.com/
---------- mupdf.info ends ----------
Nothing seems to be configurable on Mac OS for this application. All
dependencies appear to be hard coded (so fink-package-precedence is
not usable). The documentation does not list anything else than X11
as external dependencies, which appears to be confirmed by the fact
that running otool -L on the binaries shows only the following
libraries:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1197.1.1)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current
version 0.9.8)
/opt/X11/lib/libX11.6.dylib (compatibility version 10.0.0, current version
10.0.0)
/opt/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current version
11.0.0)
My first question is then, should I be satisfied with these
dependencies, or should I dig further for them (and if so, how)?
The resulting deb looks like this:
/.
/sw
/sw/bin
/sw/bin/mudraw
/sw/bin/mujstest
/sw/bin/mupdf-x11
/sw/bin/mupdf-x11-curl
/sw/bin/mutool
/sw/include
/sw/include/mupdf
/sw/include/mupdf/cbz.h
[...]
/sw/include/mupdf/xps.h
/sw/lib
/sw/lib/libmupdf.a
/sw/share
/sw/share/doc
/sw/share/doc/mupdf
/sw/share/doc/mupdf/CHANGES
[...]
/sw/share/doc/mupdf/thirdparty.txt
/sw/share/man
/sw/share/man/man1
/sw/share/man/man1/mudraw.1
/sw/share/man/man1/mupdf.1
/sw/share/man/man1/mutool.1
/sw/bin/mupdf
Would this structure require a package split, and if so what should go
where? On one hand there are no shared libraries so a split between
mupdf and mupdf-dev (or something) does not seem justified; on the
other hand there is an obvious usage difference between binaries and
headers/static libraries. I am not sure what is the proper way of
handling this kind of things.
I am also wondering whether the way I created the symlink in the
InstallScript is the proper way to go.
Finally, mupdf is released under Affero GPL, would this be covered by
the "License: GPL" field in the info file?
Advice is appreciated. Many thanks in advance.
Best regards,
Stefan
--
If it was so, it might be; and if it were so, it would be; but as it
isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass
No HTML emails and proprietary attachments please <http://bruda.ca/ascii>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
