comment on

The origin of blib folders is MakeMaker dance

$ module-starter --eumm --email email --author author --verbose --modu
+le=Structure
Created Structure
Created Structure\lib
Created Structure\lib\Structure.pm
Created Structure\t
Created Structure\t\pod-coverage.t
Created Structure\t\pod.t
Created Structure\t\manifest.t
Created Structure\t\boilerplate.t
Created Structure\t\00-load.t
Created Structure\ignore.txt
Created Structure\Makefile.PL
Created Structure\Changes
Created Structure\README
Added to MANIFEST: Changes
Added to MANIFEST: ignore.txt
Added to MANIFEST: lib/Structure.pm
Added to MANIFEST: Makefile.PL
Added to MANIFEST: MANIFEST
Added to MANIFEST: README
Added to MANIFEST: t/00-load.t
Added to MANIFEST: t/boilerplate.t
Added to MANIFEST: t/manifest.t
Added to MANIFEST: t/pod-coverage.t
Added to MANIFEST: t/pod.t
Created Structure\MANIFEST
Created starter directories and files

$ cd Structure

$ perl Makefile.PL
Checking if your kit is complete...
Looks good
Generating a dmake-style Makefile
Writing Makefile for Structure
Writing MYMETA.yml and MYMETA.json

$ gtree -f
.
|-- ./Changes
|-- ./MANIFEST
|-- ./MYMETA.json
|-- ./MYMETA.yml
|-- ./Makefile
|-- ./Makefile.PL
|-- ./README
|-- ./ignore.txt
|-- ./lib
|   `-- ./lib/Structure.pm
`-- ./t
    |-- ./t/00-load.t
    |-- ./t/boilerplate.t
    |-- ./t/manifest.t
    |-- ./t/pod-coverage.t
    `-- ./t/pod.t

2 directories, 14 files

$ dmake
cp lib/Structure.pm blib\lib\Structure.pm

$ gtree -f
.
|-- ./Changes
|-- ./MANIFEST
|-- ./MYMETA.json
|-- ./MYMETA.yml
|-- ./Makefile
|-- ./Makefile.PL
|-- ./README
|-- ./blib
|   |-- ./blib/arch
|   |   `-- ./blib/arch/auto
|   |       `-- ./blib/arch/auto/Structure
|   |-- ./blib/bin
|   |-- ./blib/lib
|   |   |-- ./blib/lib/Structure.pm
|   |   `-- ./blib/lib/auto
|   |       `-- ./blib/lib/auto/Structure
|   |-- ./blib/man1
|   |-- ./blib/man3
|   `-- ./blib/script
|-- ./ignore.txt
|-- ./lib
|   `-- ./lib/Structure.pm
|-- ./pm_to_blib
`-- ./t
    |-- ./t/00-load.t
    |-- ./t/boilerplate.t
    |-- ./t/manifest.t
    |-- ./t/pod-coverage.t
    `-- ./t/pod.t

13 directories, 16 files
[download]

Same goes for "inc", the origin is most likely inc::Module::Install - Module::Install configuration system

As for actual catalyst? I no catalyst :D

In reply to Re: catalyst folder structure by Anonymous Monk
in thread catalyst folder structure by botongdage

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.