OT: File::Spec documentation (was: Circular dependencies in PREREQ_PM)

[A. Pagaltzis]

* Ken Williams [EMAIL PROTECTED] [2004-08-27 21:16]:
 For this reason, I'm planning to roll File::Spec and Cwd into a
 single distribution.

Say, is there any chance we'll ever have the horrible mess in the
File::Spec POD cleaned up? It would be nice if the File::Spec
documentation didn't just punt you to File::Spec::Unix but
explained the common stuff itself.. as is, all the information is
strewn all over multiple modules. The first few times, perusing
that documentation is horribly annoying.

If I have hereby volunteered myself, I shall gladly take this
task upon myself -- just let me know.

Regards,
-- 
Aristotle
If you can't laugh at yourself, you don't take life seriously enough.

Circular dependencies in PREREQ_PM

[John Siracusa]

If module A uses module B, but module B also uses module A, what do I put in
PREREQ_PM?  Will the CPAN shell be able to handle a circular dependency?

-John

Re: Circular dependencies in PREREQ_PM

[Mark Stosberg]

On Fri, Aug 27, 2004 at 09:52:16AM -0400, John Siracusa wrote:
 If module A uses module B, but module B also uses module A, what do I put in
 PREREQ_PM?  Will the CPAN shell be able to handle a circular dependency?

As I understand, module A is downloaded before it is unpacked to
discover that it depends on module B. So even if B depends on A, you
already have A, so it's not a problem.

Assuming that I'm correct, the problem is only avoided because of the
current system design. If the meta data of both was downloaded first,
that could be a potential problem.

Mark

Re: Circular dependencies in PREREQ_PM

[John Siracusa]

On Fri, 27 Aug 2004 09:19:03 -0500, Mark Stosberg wrote:
 On Fri, Aug 27, 2004 at 09:52:16AM -0400, John Siracusa wrote:
  If module A uses module B, but module B also uses module A, what do I put in
  PREREQ_PM?  Will the CPAN shell be able to handle a circular dependency?
 
 As I understand, module A is downloaded before it is unpacked to
 discover that it depends on module B. So even if B depends on A, you
 already have A, so it's not a problem.

Already have means that it's somewhere in @INC, or just downloaded and
unpacked into the CPAN temp dir?

 Assuming that I'm correct, the problem is only avoided because of the
 current system design. If the meta data of both was downloaded first,
 that could be a potential problem.

Hm, I wonder if any existing CPAN modules have circular dependencies...

-John