rolfm at denison
Nov 11, 2008, 1:56 PM
Post #5 of 16
(3021 views)
Permalink
|
Somehow I totally missed this e-mail from almost a month ago. Fail.
On Oct 18, 2008, at 9:30 PM, David E. Wheeler wrote:
> On Oct 18, 2008, at 08:43, Matt Rolf wrote:
>
>> Then install Bricolage. Note I didn't do anything relating to SSL
>> or PHP Templates. BUT - *it took me less than 2 hours to install
>> with compiling and finding various packages I needed*. Red Hat, I
>> hate you. The only CPAN error I had was the Apache::SizeLimit
>> error. David, is that something that the script should be able to
>> eval?
>
> No, Bricolage turns all that over to CPAN.pm. But what was the error?
It's the same one Waldo was talking about today on the user list. It
tries to make sure it is installed, but it can't because it's already
compiled within mod_perl2.
I had thought there were changes committed to address the problem, but
looking at the commit list, I may have been hallucinating when I said
that.
> BTW, PHP::Interpreter probably won't work with Perl 5.10.
Yeah, that's how it looks.
>> When 2.0 comes out one of us should do a revised version of the
>> perl.com install article. The most glaring thing is that
>> installing Bundle::Bricolage and Bundle::BricolagePlus should not
>> be considered for 2.0. The install does a much better job of
>> finding out what is needed and those bundles are out of date in
>> regards to the Apache2, mod_perl2, and Net::SSH stuff.
>
> I've updated them, but they were always kind of more for the
> purposes of documentation than anything else. Especially since now
> you *have* to install B::BPlus in order to get mod_perl and a
> database driver. And it installs both mod_perl and mod_perl2 and
> DBD::Pg and DBD::mysql. Blech. So I agree with you.
>
> Do the READMEs need to be updated in this regard?
In various regards, yes. They vary wildly in quality/content. Some
talk about specific packages, others just list gotchas on that system.
> Also, anyone want to take a stab at adding MySQL information to
> Bric::DBA?
Maybe Waldo? :)
>> So after getting 1.11.1 up and running, what do I think? 1.11.x
>> looks much more stable than the last time I worked with it on
>> dev_elem_occurence. The interface has massive improvements in the
>> story profile - it is like a different app. I love the log
>> customization - so useful! I think there could be some
>> improvements to the primary category auto complete.
>
> Like what? (Not challenging you here, I'd just like to know so I can
> determine how feasible it is.)
For anyone who doesn't track the bugs list, I reopened the bug where
autocomplete was added with my thoughts:
http://bugs.bricolage.cc/show_bug.cgi?id=1355#c2
Feel free to add your own.
>> Fuck Opera. Erm, I mean, patches welcome. ;-P
That's not very multiplatform of you. ;) Maybe it comes down to the
support in the Javascript libraries. Perhaps a more recent version
has added Opera support?
Just out of curiosity, any particular logic behind the selection of
prototype and scriptaculous for those purposes? I know nothing about
them.
>> I've been finding/filing various and sundry bugs. I would ask
>> others to *please* do some serious, thorough testing on coherence/
>> caching issues among the desk/workspace/find/profile interfaces.
>> It has always caused problems in 1.10, but in 1.11 things still
>> seem even more unstable.
>
> Really? Huh. that sucks. :-(
I'm going to moderate my views on this somewhat as we've discussed
this at length. Some of the problems I found were due to using two
browsers. I did find one bug where a file deleted from a desk or
workspace doesn't properly get it's state set. At this point I
haven't been able to reproduce anything else. But I encourage
everyone again to test this aspect of the interface within an inch of
its life before launch.
Better late than never,
Matt
|
