This is an automated email from the git hooks/post-receive script.
kanashiro-guest pushed a commit to branch master
in repository carton.
commit e67974c5b62cf7153ef64e8e74f5f9ecf2a061ac
Author: Tatsuhiko Miyagawa <miyag...@bulknews.net>
Date: Sun Jun 26 10:08:34 2011 -0700
add back in FAQ; renamed to docs to avoid stupid gitignore in HFS
---
.gitignore | 2 +-
Makefile.PL | 6 +++---
lib/Carton/Doc/FAQ.pod | 51 ++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 55 insertions(+), 4 deletions(-)
diff --git a/.gitignore b/.gitignore
index 145a373..f691d74 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,6 +4,6 @@ Makefile
inc/
pm_to_blib
*~
-doc/
+docs/
.carton/
local/
diff --git a/Makefile.PL b/Makefile.PL
index 5a32f35..c56ccd0 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -22,7 +22,7 @@ auto_set_repository();
WriteAll;
sub doc_to_pods {
- # lib/Carton/Doc/*.pod => doc/carton-*.pod => blib/man1/carton-*.1
+ # lib/Carton/Doc/*.pod => docs/carton-*.pod => blib/man1/carton-*.1
my %pods;
@@ -30,10 +30,10 @@ sub doc_to_pods {
my $base = ($file =~ m!lib/(.*?)\.pod!)[0];
$base =~ s!/!::!g;
my $name = $base eq 'Carton' ? "carton" : ("carton-" . lc( (split
/::/, $base)[-1] ));
- my $doc = "doc/$name.pod";
+ my $doc = "docs/$name.pod";
if ($Module::Install::AUTHOR) {
- mkdir "doc", 0777;
+ mkdir "docs", 0777;
copy_pod($file, $doc, $base => $name);
}
diff --git a/lib/Carton/Doc/FAQ.pod b/lib/Carton/Doc/FAQ.pod
new file mode 100644
index 0000000..67c0a42
--- /dev/null
+++ b/lib/Carton/Doc/FAQ.pod
@@ -0,0 +1,51 @@
+=head1 NAME
+
+Carton::Doc::FAQ - Frequently Asked Questions
+
+=head1 QUESTIONS
+
+=head2 How is this different from DPAN or CPAN::Mini::Inject?
+
+First of all, if you currently use L<DPAN|MyCPAN::App::DPAN>,
+L<CPAN::Mini::Inject> or any other similar tools successfully, then
+that's totally fine. You don't need to switch to carton.
+
+If you experience difficulties with these tools, or are interested in
+what could be better in carton, keep on reading.
+
+carton definitely shares the goal with these private CPAN repository
+management tool:
+
+=over 4
+
+=item *
+
+Manage the dependencies tree locally
+
+=item *
+
+Take snapshots/lock the versions
+
+=item *
+
+Inject private modules into the repository
+
+=back
+
+Existing tools are designed to work with existing CPAN clients such as
+L<CPAN> or L<CPANPLUS>, and have accomplished that by working around
+the CPAN mirror structure.
+
+carton internally does the same thing, but its user interface is
+centerd around the installer, by implementing a wrapper for
+L<cpanm|App::cpanminus>, so you can use the same commands in the
+development mode and deployment mode.
+
+Carton automatically maintains the L<carton.lock> file, which is meant
+to be version controlled, inside your application directory. You don't
+need a separate database or a directory to maintain tarballs outside
+your application. The C<carton.lock> file can always be generated out
+of the local library path, and carton can reproduce the tree using the
+lock file on other machines.
+
+
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/pkg-perl/packages/carton.git
_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits
