Re: Module dependencies

[DrZaius]

Why not also add the minimum required version?

I suppose that needs more explenation. I would do my schema like this:

• modules -- contains information about the module, such as version, package name and so forth
• dependancies -- a cross ref that maps dependancies. Yes, this circles back to modules. This is where you put minimum required version, if set.

In this set up, you don't need to record if something is pragma or not as your modules table should contain that data.

You may also want to explore the fact that a file may contain many modules and that there are pl (perl libraries) that get loaded as well.

I also recommend writing it with a DBD::CSV backend as it could eventually replace perllocal.

[Brovnik]

Useful comments, see my Update above.

The code as written now copes with several packages per file.
I haven't so far tried to copes with perl libraries, but the EXE files listed in the pod are recorded.
As far as backends go, once it is in a DB, output is fairly easy into any format.
--
Brovnik