The project no longer bundles the plugins with the source. So I got
rid of all the Makefile logic for the plugins.
Port moved to using MODPY_PI. There is a patch for setup.py to use
the setuptools version of install which has support for
--single-version-externally-managed. I've sent this patch upstream
and it has already been committed so will be in the next release.
I discarded the old setup.py patch.
A chunk of tests fail because the PyPI tarball id missing any .aac
files from test/data. I got a patch committed upstream for their
MANIFEST.in file so that future releases will include those files.
Dependencies on ffmpeg, liboaf, and others were dropped as they
aren't needed for recent releases of picard.
Input from sthen@
ok edd@ sthen@
If somebody is removed who actually wants maintainer and either
didn't receive the mail, or didn't bother to reply to it, they are
free to send a diff to reinstate.
ok sthen@, jca@
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
Picard is the next generation MusicBrainz tagging application. This
new tagging concept is album oriented, as opposed to track/file
oriented like the ClassicTagger was.
from Amaury Gauthier (maintainer), with some tweaks
