Hi,
Every once in a while, some debug code ends up in a release.
Based on the code that I used to tighten the checks on modules loading
correctly, I could quite quickly implement checks to ban certain code
sequences. My current idea is to blacklist the following snippets:
"use Carp::Always"
"us
Hi Rob,
On Thu, Sep 10, 2015 at 9:53 PM, R. Ransbottom wrote:
> My question about user database changes was sparked by a vague
> remembrance of a text saying to use inheritance. Apparently,
> I misremembered.
>
> For myself, I am leaning toward setting up a local repository.
> I would have lik
> Well, other than the standard Perl steps "copy to blib" and "manify POD",
>> we don't really have build steps of our own. I'm indeed proposing that we
>> have a build step. I envision it to be something like this:
>>
>> * Create PostgreSQL database
>> * Play Sqitch scripts
>> * Dump schema from t
Hi Robert,
On Sat, Sep 5, 2015 at 8:27 PM, Robert James Clay wrote:
> All,
>
> On Monday, August 31, 2015 10:42:45 PM Robert James Clay wrote:
>
> > ledgersmb_1.4.15+ds.orig.tar.gz
>
>Note that a v1.4.x Debian source archive is repacked for use like that
> without the embedded Dojo libraries
Hi Joe,
Thanks for reporting (I had to dig your mail out of my spam box, due to
GMail failing to validate if it was sent by Yahoo's mail servers, hence my
somewhat late answer).
On Mon, Sep 7, 2015 at 2:21 AM, Joe Hunt wrote:
> I've been trying to install LedgerSMB 1.4.15 on Slackware Linux.
>
