[MacPorts] #43222: mkvtoolnix: upgrade to version 6.8.0
MacPorts
noreply at macports.org
Mon Jun 16 14:57:17 PDT 2014
#43222: mkvtoolnix: upgrade to version 6.8.0
-------------------------+--------------------------------
Reporter: dgonyier@… | Owner: macports-tickets@…
Type: update | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords:
Port: mkvtoolnix |
-------------------------+--------------------------------
Comment (by pixilla@…):
Replying to [comment:26 mojca@…]:
> Please don't take this as a critique, just as a teaser:
>
> Whatever you do, the result is not following the MP rules. So saying
that you split the files just in order to be compliant, doesn't sound
convincing.
The {a,b} patches in files/ is a fairly common method. The full path in
the Portfile patch is an anomaly, see below for my best guess on that one.
> How on earth do you get the whole
`/opt/local/var/macports/sources/svn.macports.org/trunk/dports/multimedia/mkvtoolnix`
with `svn diff`? I have a local sparse checkout in my home dir, I go to
that folder and `svn diff` prints just `Portfile`.
I don't know, I may have been in a hurry and did something like "svn diff
$(port dir mkvtoolnix)".
> For creating patches I usually use
> {{{
> # cd <port dir>
> sudo port extract
> # cd <port work>
> sudo git init .
> sudo git add -A
> # edit
> git diff
> }}}
> and then search-and-replace "`--- a/`" with "`--- `" to get rid of the
top level `a/` and `b/`.
I copy the sources to {a,b} so I don't loose changes if I forget to add
"port -k -o" after a Portfile edit.
> Can you please test whether `+wxwidgets` does anything useful?
I'll try again, the gui did not work for me a few days ago.
--
Ticket URL: <https://trac.macports.org/ticket/43222#comment:27>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list