On Sun, Mar 10, 2013 at 4:20 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 8 Mar 2013, at 04:57, Francisco Obispo fobi...@isc.org wrote:
They are installed by default under the lib/ directory, I'm not a big fan of
that setup,
Nobody is a big fan of this setup.
I don't think the problem
On Mon, Mar 11, 2013 at 1:29 PM, Alejandro Imass
alejandro.im...@gmail.comwrote:
This pre-dates Module::ShareDir.
So the templates, images (i.e. the /root) are considered shared data?
When I was converting our Catalyst apps to use Dist::Zilla I looked at
changing where Catalyst looks
On 8 Mar 2013, at 04:57, Francisco Obispo fobi...@isc.org wrote:
They are installed by default under the lib/ directory, I'm not a big fan of
that setup,
Nobody is a big fan of this setup.
This pre-dates Module::ShareDir.
If someone was to fix things such that new applications installed
Yes,
By we I mean: Internet Systems Consortium (ISC), internal applications.
We use debian in some of our platforms, and we package our software into a
private repo.
Apologies for the confusion ;-)
On Mar 10, 2013, at 3:00 PM, gregor herrmann gre...@debian.org wrote:
I'm not aware of
On Thu, Mar 7, 2013 at 8:57 PM, Francisco Obispo fobi...@isc.org wrote:
Module::Install lets you do some limited configuration, but if you're
looking to customize it, you're better off with a custom distribution
package.
A bit off the topic, but I've been using Dist::Zilla to help package
On Fri, Mar 8, 2013 at 3:24 AM, Bill Moseley mose...@hank.org wrote:
On Thu, Mar 7, 2013 at 8:57 PM, Francisco Obispo fobi...@isc.org wrote:
Thanks to both of you for your valuable insight.
We've also looked at the PAR route. Up until now we've always
installed manually and only used the
On Fri, Mar 8, 2013 at 1:43 PM, Alejandro Imass
alejandro.im...@gmail.comwrote:
Thanks to both of you for your valuable insight.
We've also looked at the PAR route. Up until now we've always
installed manually and only used the Makefile to keep track of
dependencies and easier installs of
On Fri, 08 Mar 2013, Bill Moseley wrote:
A bit off the topic, but I've been using Dist::Zilla to help package
Catalyst apps. My favorite features are auto versioning, managing the
Changes file, and automatic dependency creation. And, of course, having a
custom PluginBundle that centralizes
Hi,
What is the canonical way to use the provided Makefile to deploy
Catalyst apps. Up until now I've only used to mainatin the
dependencies and use make and make test but I have never used make
install.
I read through the Makefile and it's obvious that it will install all
modules where they
The installer uses Module::Install
So basically:
1) lib/ is installed in: /usr/local/lib/perl5
2) script/* becomes /usr/local/bin/*
3) man pages are usually installed in /usr/local/share/man/man3/
etc.
perldoc Module::Install for more info ;-)
dh-make-perl if you want to make a debian/ubuntu
On Thu, Mar 7, 2013 at 6:03 PM, Francisco Obispo fobi...@isc.org wrote:
The installer uses Module::Install
So basically:
1) lib/ is installed in: /usr/local/lib/perl5
2) script/* becomes /usr/local/bin/*
3) man pages are usually installed in /usr/local/share/man/man3/
etc.
perldoc
They are installed by default under the lib/ directory, I'm not a big fan of
that setup, so what we usually do (in debian), we setup a custom package that
does the magic that we need, including the nginx setup, etc.
Module::Install lets you do some limited configuration, but if you're looking
12 matches
Mail list logo
