many ruby/rubygem ports: death of rubyforge.org
rubyforge.org shutdown on May 15, 2014. This commit accounts for that by doing
several things:
- Deprecate ruby that had only rubyforge.org as MASTER_SITES (and so are now
only fetchable via our cache)
- Deprecate ports that depend on those
- Update the WWW pkg-descr line that points to rubyforge.org for rubygem ports
(which are still fetchable from rubygems.org)
The next step will be to remove rubyforge.org from bsd.sites.mk, after these
deprecated ports are deleted.
Phabric: D591
With hat: ruby
Approved by: portmgr (because of committing to unstaged graphics/mingplot port)
Update to 6.8.9-3 [1][3].
Use USES=compiler:openmp for the OPENMP option[2]
Ditch the use of perl for patching etc [4] and silence perl threaded check [6]
-delay option spurious message should be fixed [5]
JASPER option was replace by JPEG2000 for JP2k support.
Put 16BIT_PIXEL and HDRI option separate option block. These options change
the library name, so the user needs to take this into consideration.
Use new LIB_DEPENDS syntax.
Use @sample for config files.
Sprinkle some USES=pkgconfig for some ports, since we don't pull it in
anymore at run-time.
PR: 185462 [1]
PR: 187548 [2]
PR: 182793 [3]
PR: 181746 [4]
PR: 176047 [5]
PR: 190814 [6]
Submitted by: c.petrik.sosa@gmail.com [1]
Matthieu Volat <mazhe@alkumuna.eu> [2]
free.bsd@webstyle.ch [3]
andrnils@gmail.com [4]
rfg@tristatelogic.com [5]
Michelle Sullivan <michelle@sorbs.net> [6]
Approved by: portmgr (blanket) (for NO_STAGED ports)
Remove indefinite articles and trailing periods from COMMENT, plus
minor COMMENT typos and surrounding whitespace fixes. Categories G-I.
CR: D201
Approved by: portmgr (bapt)
- Mark BROKEN: does not configure
checking for ImageMagick version >= 6.4.9... yes
checking for HDRI disabled version of ImageMagick... no
Can't install RMagick 2.13.1.
RMagick does not work when ImageMagick is configured for High Dynamic Range
Images.
Don't use the --enable-hdri option when configuring ImageMagick.
Reported by: pointyhat
- Return my ports back to the pool. I was unable to make any fixes to
my ports in the past 3 weeks while ports were broken on any 10.x
machines, which means I'm unable to maintain them. So let people know
that there's no available support for them until things are back to
normal (which also means that anyone with spare time will be able
to fix them without getting approval).
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
- Don't fail if some tests fails. It is needed if some features in
ImageMagick are missed (e.g. GS support). Rmagick doesn't check if all
features are available when running tests.
Reported by: demon@
* Update to 1.12.0.
* remove BUILD_DEPENDS of wmf, since it should addressed in
GraphicsMagick or ImageMagick
* Propagate the NOPORTDOCS setting to the software build using
--disable-htmldoc on the configure script
PR: ports/98907
Submitted by: Rui Lopes <rgl_AT_ruilopes dot com>
[PATCH] Update port: graphics/ruby-rmagick to 1.9.3
Updates RMagick to the latest release, 1.9.3. Also adds an option to
build against GraphicsMagick rather than ImageMagick.
PR: ports/90886
Submitted by: Nick Muerdter <spam@nickm.org>
Bump portrevision and dependency on ImageMagick
in order to trace recent ImageMagick update.
Submitted by: Arjan van Leeuwen <avleeuwen@piwebs.com>
PR: ports/74487
Approved by: mat
Reviewed by: lofi
Chase the master site's HTTP redirection.
Mark unBROKEN. This port is not broken itself but fails to build
because ImageMagick is somehow built without the FreeType support
enabled although the --with-ttf flag is given.
Add ruby-rmagick (RMagick), a binding for ImageMagick. Defines
approx. 120 methods for 2D image manipulation. HTML documentation
contains usage guide and API reference, including 116 complete example
programs and images.
Make sure that you have the latest version of libwmf (>= 0.2.7) before
installing this library. libwmf 0.2.6 seems to have a bug that causes
coredump.
