Early Draft of Bugzilla Dev Setup

[Dylan Hardison]

On Sat, May 14, 2016 at 11:29 PM, Jeff Fearn <jefffearn at gmail.com> wrote:
> On 14/05/2016 12:33 AM, Dylan Hardison wrote:
>>
>> On Fri, May 13, 2016 at 9:30 AM, Gervase Markham <gerv at mozilla.org> wrote:
>>>
>>> On 13/05/16 03:28, Dylan Hardison wrote:
>>>>
>>>> This post has been rattling around in my head for a bit.
>>>> Eventually it needs to end up in docs.
>>>>
>>>>
>>>> http://dylanwh.tumblr.com/post/144277013247/developing-bugzilla-with-plackup-and-cpanminus
>>>
>>>
>>> Awesome! How can we make it even simpler? Ideas:
>>
>>
>> In general I'm about avoiding magic incantations. Adding an
>> automagical --dev flag might be too much.
>> What we can definitely do is include a reasonable answers.txt file and
>> have the instructions for running checksetup include that.
>>
>> perl checksetup.pl --cpanm contrib/devmode.txt
>>
>> a command to run the plackup with dev settings is good though, and
>> I've filed a bug about that. The name will be something that implies
>> "this is for development, you probably want something else in
>> production".
>>
>> Meanwhile, making more defaults work -- when should we have a
>> discussion about moving the perl modules under 'lib' as is common
>> practice? :)
>
>
> 10 years ago :) Would extensions move to lib/Extension/?
Maybe. If we wanted the namespaces to make sense we'd put them under
Bugzilla/Extension/*...
There are a few problems with extensions (look at Extension.pm)
there are unneeded closures being created. Each extension gets its own
hook in @INC, for instance.