Bug 100885 - [NEW PORT] devel/p5-Config-ApacheFormat Read apache-style config files
Summary: [NEW PORT] devel/p5-Config-ApacheFormat Read apache-style config files
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Roman Bogorodskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-26 16:40 UTC by Martin Tournoij
Modified: 2006-07-26 21:22 UTC (History)
0 users

See Also:


Attachments
file.shar (3.56 KB, text/plain)
2006-07-26 16:40 UTC, Martin Tournoij
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tournoij 2006-07-26 16:40:13 UTC
This module is designed to parse a configuration file in the same
        syntax
        used by the Apache web server (see http://httpd.apache.org for
        details). This allows you to build applications which can be easily
        managed by experienced Apache admins. Also, by using this module,
        you'll benefit from the support for nested blocks with built-in
        parameter inheritance. This can greatly reduce the amount or
        repeated
        information in your configuration files.

        A good reference to the Apache configuration file format can be
        found
        here:
        http://httpd.apache.org/docs-2.0/configuring.html

        Authors: Sam Tregar <sam@tregar.com>, Nathan Wiger <nate@wiger.org> 
        WWW:
        http://search.cpan.org/~samtregar/Config-ApacheFormat-1.2/
Comment 1 Roman Bogorodskiy freebsd_committer freebsd_triage 2006-07-26 20:07:01 UTC
Responsible Changed
From-To: freebsd-ports-bugs->novel

I will take it.
Comment 2 Roman Bogorodskiy freebsd_committer freebsd_triage 2006-07-26 20:54:59 UTC
State Changed
From-To: open->closed

New port added, thanks! 

Two notes: 
1. Authors: is not `official' pkg-descr keyword and should be 
   avoided.  
2. When creating a shar, don't use absolute pathes (i.e. /usr/ports/new/port), 
   but use "shar `find port` like it's said in the Porters Handbook.