id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,lang,patch,platform
788,Audit PDD30 compliance,jkeenan,jkeenan,"Parrot Design Document 30:  Installation (''docs/pdds/pdd30_install.pod'') defines the locations where Parrot is to be installed.  To help resolve other Trac tickets concerned with installation-related issues, it would be helpful to audit our '''current''' compliance with PDD30.  Assuming that you configure as follows:
{{{
perl Configure.pl --prefix=/path/to/install/tree
}}}
... and then call `make`, what happens when you then call `make install` and/or `make install-dev`?  Is the resulting file tree under ''/path/to/install/tree'' that which you would predict on the basis of PDD30?

We need a report that identifies all files installed and flags those files which do not clearly match the criteria established in PDD 30.

Report should be provided as an attachment to this TT.

Thank you very much.[[BR]]
kid51",patch,closed,normal,,install,trunk,medium,fixed,install PDD30,pmichaud wayland particle,,applied,all