|
From: Ken Youens-C. <ky...@gm...> - 2005-04-18 22:01:13
|
On Apr 15, 2005, at 2:41 PM, Chris Winters wrote:
> You're doing it the right way. The other useful workflow is to edit
> the live website files (especially for templates/HTML files) and once
> you're done run a 'update_package' command to sync your development
> package from the live package.
I had trouble running the "update_package" command with
OpenInteract-1.99_06's "oi2_manage." It kept telling me I wasn't
providing a valid "package_dir." I traced the error to
"OpenInteract2::Manage::Website::UpdatePackageFromWebsite." It was
looking for the file "package.conf" in the "package_dir," but only
"package.ini" exists. Here's a diff:
$ diff -cu UpdatePackageFromWebsite.pm UpdatePackageFromWebsite.orig
diff: conflicting specifications of output style
--- UpdatePackageFromWebsite.pm Mon Apr 18 16:49:44 2005
+++ UpdatePackageFromWebsite.orig Mon Apr 18 16:49:28 2005
@@ -56,7 +56,7 @@
return "Must be a valid directory";
}
my $changelog = catfile( $param_value, 'Changes' );
- my $package_conf = catfile( $param_value, 'package.ini' );
+ my $package_conf = catfile( $param_value, 'package.conf' );
unless ( -f $changelog && -f $package_conf ) {
return "Does not appear to be a valid package directory";
}
And now it works. Schweet!
BTW, if I'm really trying to get going with OI2, should I be using the
"developer" version of 1.99 or should I downgrade to the 1.62 version?
If I should be bleeding-edge, should I be working with the CVS version
or stick to the CPAN developer release?
ky
|