- Now depends on newer gcc, use 4.6 by default.
- Enable webkit2 api in the gtk3 FLAVOR. Still broken/erratic behaviour at
runtime, but at least this will allow people to debug it, and it's
required by newer GNOMEs anyway. Provide MiniBrowser for debugging purposes.
- add hack from bug #118732 to workaround the fact that our binutils
doesnt support 'ar T'
- update patches from #103128 to tentatively fix powerpc runtime
- force-disable YARR_JIT & ASSEMBLE on archs without JIT (ie anything
besides i386/amd64) via Platform.h patch instead of JSC_CPPFLAGS (which
doesnt work anymore anyway)
- add a bunch of patches to fix build (missing includes etc) in the WebKit2
source tree
Tested in an amd64 bulk build, runtime-tested previous betas on
i386/amd64, test-built on powerpc and sparc64. Things might still be
broken at runtime on powerpc, but at least it allows more GNOME things
to be updated.
This script is intended to help you watch URLs and get notified (via
email or in your terminal) of any changes. The change notification will
include the URL that has changed and a unified diff of what has changed.
The script supports the use of a filtering hook function to strip
trivially-varying elements of a webpage.
- is unmaintained/outdated for years
- has a lot of PLISTed files that change during usage
- @comment no checksum or @sample don't help here
suggested by and ok aja@, ok sthen@
instead. It is just too hard to maintain a coherent list of still
reachable homepages for GNOME projects so use wiki.gnome.org which is
the entry point for *all* GNOME apps.
- ezpublish, no maintainer, last updated 2009/08/24
- mantis, no maintainer, out of date
- phplist, very outdated and no-one maintains it
- phpmemcachedadmin, port only extract the distfile and that's it
- vtigercrm, port only extract the distfile and that's it
While we do this in a case-by-case basis, this was done for one of the
following reasons:
* do not give user a sense of security because there is a pkg available
when it is in fact outdated/unmaintained and including possible security
issues
* package with no added value besides extracting the distfile under
/var/www are pretty useless -- they demand an effort to be kept up to
date for no benefits (except if someone actually maintains it of course)
* some webapps must complete a strict version update path -- eg.
updating from 1.0 to 1.5 requires updating to 1.1, 1.2, 1.3 and 1.4
first -- that does not work well with pkg
ok Wen Heping (MAINTAINER of vtigercrm)
ok sthen@ jasper@ robert@
PS: no we are not in a rampage to remove lots of www apps -- just some when
it makes sense
