was OK sthen@
additionally update rc script to latest changes (patch and OK from ajacoutot@).
Will be enabled after I find time to test on a clean system.
Plack is a set of tools for using the PSGI stack. It contains middleware
components, a reference server and utilities for Web application
frameworks. Plack is like Ruby's Rack or Python's Paste for WSGI.
See PSGI for the PSGI specification and PSGI::FAQ to know what PSGI and
Plack are and why we need them.
From MAINTAINER Abel Abraham Camarillo Ojeda on ports@
This document specifies a standard interface between web servers and
Perl web applications or frameworks, to promote web application
portability and reduce the duplicated efforts by web application
framework developers.
From Abel Abraham Camarillo Ojeda on ports@
Rainbows! is an HTTP server for sleepy Rack applications. It is based
on Unicorn, but designed to handle applications that expect long
request/response times and/or slow clients.
ok landry
Unicorn is a HTTP server for Rack applications designed to take
advantage of features in Unix/Unix-like kernels and only serve
fast clients on low-latency, high-bandwidth connections.
ok landry
Railties is responsible for gluing the parts of Ruby on Rails together.
Overall, it:
* handles the entire bootstrapping process for a Rails application;
* manages the rails command line interface;
* provides the core Rails generators;
ok landry
Rack::Test is a small, simple testing API for Rack apps. It can be used
on its own or as a reusable starting point for Web frameworks and
testing libraries to build on.
ok landry
Rack::Mount is a stackable dynamic tree based Rack router. Rack::Mount
supports Rack's +X-Cascade+ convention to continue trying routes if the
response returns pass. This allows multiple routes to be nested or
stacked on top of each other. Since the application endpoint can trigger
the router to continue matching, middleware can be used to add arbitrary
conditions to any route. This allows you to route based on other request
attributes, session information, or even data dynamically pulled from a
database.
ok landry
Canto is an Atom/RSS feed reader for the console that is meant to be
quick, concise, and colorful. It provides a minimal, yet information
packed interface with almost infinite customization and extensibility.
OK landry@
This module adds PHP-based password strength checking and validation
routines that mirror the jQuery routines, so that administrators can
restrict passwords to only be, for example, "high" strength. The module
simply modifies existing password confirm fields (where two passwords
are entered, like the user edit form), so no other setup is required
beyond configuring the desired enforcement rules.
ok landry@
is a configuration file, even though it's buried deep in code
directories. Pointed out by Tobias M. Boelz <tmb at usta dot de>.
Thus, use @sample and bump.
OK espie@ stephan@
Previously, we were using ruby->=1.8,<=1.9, instead of
ruby->=1.8,<1.9. While this wouldn't cause an issue, since
our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9,
it's still wrong and should be fixed. This also fixes the
following minor issues:
Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS.
Currently we don't have a ruby port that uses FLAVORs that
would differ from MODRUBY_FLAVOR, but it's possible we will
in the future.
Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in
REGRESS_DEPENDS. This probably is not strictly necessary, but
BUILD_PKGPATH is used in more cases, so it is good for
consistency.
Switch to new style *_DEPENDS, with the version specification
at the end. The remaining cases where this is not done is
because a specific version is used.
Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if
the old version is installed when you run a regress test, it
will install the new version first.
Some conversion of spaces to tabs for consistency.
OK landry@
DESCR:
SOGo is a groupware server built around OpenGroupware.org (OGo) and the
SOPE application server, with a focus on scalability. It provides the
usual groupware functionality as E-Mail, Calendaring, and Contacts
management.
Not yet linking it to the build, fixing last few things in the tree.
OK landry@, sthen@
crash under some circumstances where the linux qt libs fail to load
if one is running a panel which then ends up in a hard crash of opera
(which in turn can hangs the entire display)...
ok jasper@
fixes a session reuse issue even though this release has not been tagged
as 'security relevant'. Details at http://drupal.org/node/967244.
Make sure you upgrade all files while you're logged in (or have access
to settings.php) otherwise you'll lock yourself out pretty easily, in
case you use Captcha for logins. Database upgrade required, too.
- fix PF nat rules for nat-to
- add missing @conflict for jakarta-tomcat-examples (for people
upgrading from really old packages; niklas@ hit this upgrading
a machine from 3.8 :-)
tweaks/ok jasper@
- install drupal modules/themes as root:daemon rather than www:www
(only the files/ directory needs to be writeable by 'www').
- don't install 'settings.php' world-readable since it contains the
DB password. Use 640, owner 'www' instead.
- bump all modules.
tested in production, including upgrade szenarios.
ok sthen@ and landry@, maintainer timeout.
PKG_ARCH = * removed from many ports as it is added automatically
for pure ruby gem ports. Switch ports that previously used
GEM_SKIPDEPENDS to adding dependencies or modifying the underlying
gem metadata with patches.
OK landry@
allow webkit to build (and even run!) on mips64el, many thanks !
Patches will probably need to be reworked so that they can be fed
upstream, but at least this allows another part of the tree to build on
loongson. And this might even work for sgi.
Tested by jasper@
infrastructure/mk/bsd.port.mk to fix pkg-readmes ownership.
RackMonkey is a tool for managing racks of equipment such as servers
and switches. You can keep track of what's where, which OS it runs,
who it belongs to and what it's used for. RackMonkey quickly finds
any device and draws a rack diagram of its location.
This group of modules is sort of a recipe module that makes things
easier by showing how to integrate some other modules as well as
providing miscellaneous features that aren't distributed by Views
itself. Sometimes these modules are only base recipes that will
need to be themed and spiced up to fit your needs.
Ubercart is an e-commerce suite developed for Drupal. It has been
designed with the end user in mind, focusing on usability in three key
areas: store configuration, product and catalog creation, and order
administration. On the front end, all major systems are configurable and
integrate with the standard Drupal systems (node, taxonomy, user, etc.).
On the back end, the settings pages and order administration pages have
been designed with ease of use in mind.
The Frequently Asked Questions (faq) module allows users, with
appropriate permissions, to create question and answer pairs which
they want displayed on the 'faq' page. The 'faq' page is automatically
generated from the FAQ nodes configured.
package. Teach users how to properly report bugs, and add a
run-mozilla.sh patch so that it finds our gdb. While here remove
updates/ subdir at uninstall time, otherwise it stays..
The Session API is a very simple set of functions that extend the core
sessions workings, allowing data to be stored and associated with a
user's session.
