the use of the ruby18 FLAVOR to explicitly build a version for ruby 1.8.
To handle updates, add a @pkgpath marker with the unflavored PKGPATH
to all ruby18 FLAVOR gem/extconf PLISTs.
Remove format-executable CONFIGURE_STYLE, since only one port uses it.
Instead, allow the port Makefile to set GEM_FLAGS, and have ruby.port.mk
append to that if it already exists.
clean it up.
More recent gcc have a cleaner fix, where fixincludes has been moved to
another directory that it truly owns, but in our case, we do not need to
clean up the fake directory as it's just been created.
okay pascal@, naddy@
- remove useless patch to gfx/thebes/Makefile.in adding -lpangox-1.0 to
EXTRA_DSO_LDOPTS, this was maybe useful before ffx 3.0, but mozilla
stopped using pangox between 2.0 and 3.0. See for the last traces of
pangox.h use : https://bugzilla.mozilla.org/show_bug.cgi?id=528941. See
also bugs #323671/#338446
- backport the patch from #528941 to remove useless pangox.h inclusion
from www/firefox35.
- remove the RUN_DEPENDS on pangox-compat
- bump all corresponding REVISIONS
- while here, make sure all moz ports depend on latest nspr 4.9.2 since
it'll be a requirement for upcoming gecko 16 releases
FocusWriter is a simple, distraction-free writing environment. It
utilizes a hide-away interface that you access by moving your mouse to
the edges of the screen, allowing the program to have a familiar look
and feel to it while still getting out of the way so that you can
immerse yourself in your work.
ok sthen@
Initially as a patch for plugins-bad (where the sndio(7) module is
located upstream) -- but it makes no sense to install the whole kitchen
sink just to have sound -- so move it into plugins-base and adapt the
plumbing accordingly.
big thank you to ratchov@ for his work on this!
The situation is this: even when we --disable-gtk-doc, if gtk-doc is
actually installed at configure stage, tools like gtkdoc-rebase will be
picked up and run during the install target. That is bad because the
gtk-doc package may have been removed by then, especially during dpb(1)
bulks (we explicitely disable support for it so why should it stay...).
So for now, let's add the following env to configure whenever we use
--disable-gtk-doc, until a bettersolution is found...
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
ac_cv_path_GTKDOC_REBASE="" \
ac_cv_path_GTKDOC_MKPDF=""
