Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#34011 closed defect (fixed)

yorick-av @0.0.1: add devel variant

Reported by: paumard Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: haspatch Cc: neverpanic (Clemens Lang)
Port: yorick-av

Description

Hi,

as discussed here:

http://lists.macosforge.org/pipermail/macports-dev/2012-April/018662.html

the current ffmpeg dependency does not work reliably due to the binary-incompatible ffmpeg/ffmeg-devel dichotomy. If a user already has ffmpeg-devel and installs the yorick-av binary package, yorick-av simply does not work.

The suggested solution is to provide two variants and select the right one at install time.

I am not sure if this requires a revision bump (the current binary package is correct for the -devel variant). Also, please fill free to rename the variant (e.g. to "ffmpeg-devel" instead of simply "devel").

In addition, this updated portfile:

  • adds openmaintainer as a co-maintainer,
  • uses a path dependency for yorick to ease the task of using a custom yorick build. Yorick versions are (almost?) always binary compatible.

Best regards, Thibaut.

Attachments (1)

yorick-av-devel-variant.diff (1.0 KB) - added by paumard 12 years ago.
use a variant instead of path: dependency for ffmpeg/ffmpeg-devel

Download all attachments as: .zip

Change History (6)

Changed 12 years ago by paumard

use a variant instead of path: dependency for ffmpeg/ffmpeg-devel

comment:1 Changed 12 years ago by neverpanic (Clemens Lang)

Cc: cal@… added
Keywords: haspatch added

I assume you are the maintainer? You didn't open the ticket using the email address listed in the Portfile.

In the future, setting keywords to "maintainer" and "haspatch" might get your ticket more attention and a quicker commit.

comment:2 Changed 12 years ago by paumard

Yes, I'm the maintainer, thanks for the tip. I Don't think I can change keywords after the ticket is created.

comment:3 Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: fixed
Status: newclosed

r91981. What's the reasoning behind changing the yorick dependency to a path-style dependency, if I may ask? Do you plan adding a yorick-devel port?

comment:4 Changed 12 years ago by paumard

Thanks.

I don't plan to make a public yorick-devel port, but I think it's good to give our users the ability to do so for themselves. Note that if ${prefix}/bin/yorick is a symlink to a yorick binary outside of the macports tree, a source install of the plug-in packages should correctly install them for this instance of yorick, out of the macports tree.

Regards, Thibaut.

comment:5 Changed 12 years ago by neverpanic (Clemens Lang)

Oh, now I see you actually explained that in the ticket text, sorry for missing that.

MacPorts usually is self-contained and doesn't depend on whatever a user has manually installed, but as port maintainer I guess this is up to you. Please remember depending on an external yorick binary is not supported (as in supported by base), though.

Note: See TracTickets for help on using tickets.