#29442: gstreamermm 0.10.9.1 Port -------------------------------+-------------------------------------------- Reporter: arcnorj@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gstreamermm -------------------------------+-------------------------------------------- Comment(by arcnorj@…): Replying to [comment:3 ryandesign@…]:
Replying to [comment:2 arcnorj@…]:
Sorry, this is my first port and didn't have the time to test with an empty Macports installation.
No problem; we wouldn't expect you to go to that trouble; I know I don't. But that's why I at least try to install submitted ports before committing them, to make sure there's at least two people who were successful in building the port.
* I added bzip2 like in the example portfile that adds zlib. I thought it was needed for the extracting of the package (as is a tar.bz2 package, but .tar.gz packages are also provided). Do you mean that I don't have to add the bzip2 dependency if I add the use_bzip2 flag, or that I can simply use the gz packages?
If you mean the [http://guide.macports.org/#development.examples.basic rrdtool portfile example shown in the guide], then the reason it lists a library dependency on zlib is that the rrdtool software actually uses the libz.dylib library. All the extract options (use_bzip2, use_zip, use_xz, use_7z) automatically add the necessary extraction utilities to depends_extract; you don't have to do anything extra. It's preferred to use the smallest distfile, so since bz2 files are smaller than gz files, use bz2 files when available. Unless xz files are available, which are even smaller. Note that by the way the zlib port is for the libz library, while the utility used to extract .gz files is the gzip program, available in the gzip port. Yeah, I mean there. I see, I didn't check the exact port and just assumed that was for the extracting part. My mistake. And also, of course I meant the gzip port, silly mistake :P
* I used cairomm-devel because is the most recent version and the one I tried, but I can try to compile it with cairomm to see if it works.
cairomm-devel is for the most recent ''development'' version, while cairomm is for the latest ''stable'' version. (Well, it's supposed to be, but actually I see cairomm is a version behind; I've filed #29450 asking for it to be updated.) So yes, please depend on cairomm, if that will function; -devel ports should not be listed as dependencies, unless the software will not work with the latest stable version and actually requires a newer development version. Also, when declaring dependencies on ports which have -devel and non-devel versions, use path:-style (not port:-style) dependencies; see #14540.
* I added md5 checksum because other ports and the Macports guide have them.
md5 checksums are being removed from other ports as they're updated, if the person updating the port remembers to do so. I'll work on removing references to md5 checksums from the guide. Ok, removed.
* I'll do that [[br]] [[br]] As per the error, it seems that gstreamer-plugins-? is really needed (but the documentation didn't say anything about it). I'll try to narrow down to the least requirements and repost the portfile.
I'll bet some of these ports are needed? {{{ $ port echo name:gst-plugins gst-plugins-bad gst-plugins-base gst-plugins-gl gst-plugins-good gst-plugins-ugly }}} Yes, those are the ports needed, but in theory only gst-plugins-base is really needed. I'll try to uninstall them from my system and check the really needed ones, and try to add the optional ones as variants or something like that.
Thanks for your help!
Thank you!
-- Ticket URL: <https://trac.macports.org/ticket/29442#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS