Re: [Module::Build] codebase? paths in .tar.gz?

[Randy W. S. <Ra...@Th...>]

On 12/20/2003 12:10 PM, Glenn Linderman wrote:

> So that is good, I guess, even if it means that all the tar programs in 
> the world are broken except GNU tar 1.13, and A::T.  (One cannot help 
> but wonder instead if GNU tar 1.13 and A::T are the ones that are broken.)

Well this atleast proves that the paths are there, thus it is not a 
problem with M::B, but I think this is going to be a big issue for 
Windows users. I think if it's possible for Archive::Tar to be better 
compatible with other tools, it should. If I knew anything about the tar 
  format, I'd try to provide a patch. Since I don't, I'll just cc the 
maintainer. ;-)

> Unfortunately, there still seems to be one major outstanding problem: 
> installing my module using PPD does not cause my files to be copied into 
> the c:\perl directory tree.
[...]

> Now I suppose, since this is my first module, that I could have left out 
> something.  But somehow, "perl build install" figured out how to install 
> the module successfully (albeit, it doesn't create the two files above, 
> which seems to be a PPM record of configuration, so that is probably 
> correct).  However, using the same environment, and creating the "perl 
> build dist" and "perl build ppd" (with a hand edit to the PPD for 
> version-checking... oh, should that have been in the patch?  That's 
> another unresolved issue, I think), followed by "PPM install", does not 
> place the files where they belong.  So if there is something missing, I 
> guess that Cookbook needs some more help.  Or if it is some other 
> reason, perhaps M::B should be improved to deal with it?

No, you haven't missed anything. It should work. I suspect the problem 
is related to the problem with the tar format. I don't understand though 
why. Module::Build uses Archive::Tar to create the dist. ppm uses 
Archive::Tar to unpack it. I hate ppm, but I guess I'll see if I can 
trace though and see what the problem is.

Randy.