Hello, At 21:15 -0800 on 2014-11-13 Alexander Hansen wrote: > > > On Nov 13, 2014, at 8:06 PM, Stefan Bruda <ste...@bruda.ca> wrote: > > > > 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: > > > > 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 libcrypto dependency indicates that system-openssl-dev would be > in order as a BuildDepend.
Understood. I will dig some more but I don't think I will find anything else. > > 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. > > You can do a monolithic package if you like. Or you could divide > it up into runtime and development portions (mupdf and libmupdf, > maybe) Thank you, I will just take the easy way out, ;-) especially since the whole package is small. > > I am also wondering whether the way I created the symlink in the > > InstallScript is the proper way to go. > > Sure. It’s best to do it in the InstallScript, by whatever method > you like, rather than in a PostInstScript, so that it is included > in the .deb. Great. > > Finally, mupdf is released under Affero GPL, would this be covered by > > the "License: GPL" field in the info file? > > That would be OK, yeah - I believe the "Affero" distinction refers > to embedding into web-based services. I believe that you are perfectly right. > If there's a specific version mentioned, like GPLv3, use that. > Make sure to include a file which has the license in it, like > COPYING. Great again. I will open a ticket for the package then (as soon as I double check the dependencies), in the hope that others might find mupdf useful. Many thanks! 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
