Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of mab2001@gmail.com designates
 209.85.211.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:content-type;
        b=mBtyWVJtlcronMZ/uv9AyyUghljpGBvbNrdQTBcFV9fiDeKkGTz5PtFLpX9FrIeu9H
         /zADHts5PtlIVecEkY0BtBW7z6TA8zK3Y4IPGGQSg4BzV8Q+wKHu0F76d0lJ0U0PiyS6
         Dns0oe/pC17Vb6MIzmrd5Sz9Gbei56MLOImCM=
MIME-Version: 1.0
Sender: mab2001@gmail.com
From: Mike Barborak <barborak@basikgroup.com>
Date: Thu, 10 Sep 2009 09:55:04 -0400
Message-ID: <b6c5c4be0909100655n722b8914pfa945dc3dd0d63ca@mail.gmail.com>
Subject: distributing software built on mod_perl
To: modperl@perl.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hello,

We have built some software that depends on mod_perl and are working
on how to distribute it to customers and have them install it. It
seems the task we're asking of our customer is not for the faint of
heart as it involves a lot of command line operations, an
understanding of their web server installation, and the ability to
install mod_perl and some number of Perl modules on which our software
depends. Standing at the foot of this documentation and installation
script mountain, we're looking for trails blazed by those who have
come before.

So, can anyone point me at other software with these requirements and
their solution to this problem? Particularly ones that have handled
theses issues well?

Alternately, do you think our approach is fundamentally unsound for
our intentions? Is there a better way to write and distribute Apache
modules?

Thanks,
Mike


Mike Barborak
Technical Director
barborak@basikgroup.com

------------------------------------

BASIK GROUP
1201 Broadway, #704
New York, NY 10001

office: 646 201 9347
cell: 646 263 7029
www.basikgroup.com