in reply to How to clean-up an autobundle so it's really "auto-installable"

It would seem that instead of creating a "bundle" (which seems to be a rather magic thing), it might be easier to just create an empty module that depends on the modules it should bundle.

Modern CPAN installers like App::cpanminus are quite capable of actually installing recursive dependencies, so the first installing attempt should succeed.

<update> It seems that what I suggested is implemented as Task, so maybe an autotask script would be in order? </update>

Granted, it neither answers your question (I don't have a tool that does it automatically) nor does it solve the problem of modules being compiled conditionally, but maybe it gives you food for though.

What you seem to want is a topological sort of the depency graph - maybe Sort::Topological and the data from http://deps.cpantesters.org/ could help you here.

  • Comment on Re: How to clean-up an autobundle so it's really "auto-installable"
  • Download Code

Replies are listed 'Best First'.
Re^2: How to clean-up an autobundle so it's really "auto-installable"
by locked_user sundialsvc4 (Abbot) on Jun 16, 2011 at 15:41 UTC

    Very probably so.   Specific details are needed with regard to your various suggestions.   I see no references in CPAN, etc. to tell me, “what is autotask?”

      "autotask" is my suggested replacement (but not yet written by anybody) for autobundle, that works the same but creates a Task instead of a Bundle.