logo       
Google Custom Search
    AddThis Social Bookmark Button

Re: 5.8.6 - t/lib/vmsfspec.t missing from manifest.: msg#00040

Subject: Re: 5.8.6 - t/lib/vmsfspec.t missing from manifest.
 
On Tuesday, March 15, 2005, at 08:56AM, John E. Malmberg 
<malmberg@xxxxxxxxxxxxxxxxx> wrote:

>It appears that the file t/lib/vmsfspec.t is missing from the manifest.
>file.

It's generated at build time so it should not be in the manifest.

$ search [.vms]descrip_mms.template "vmsfspec.t :"/win=2
[.t.lib]vmsfspec.t : [.vms.ext]filespec.t
        Copy/NoConfirm/Log $(MMS$SOURCE) $(MMS$TARGET)

>Is there a perl script that will identify all files that are present in
>the unpacked directory except for the ones in the manifest or where
>generated by the build procedure?

Test::Smoke may have something like that.  In general, though, for the core 
build we need to check the manifest before we have Perl, so it's done in DCL in 
configure.com.

>Also it appears that magic.t is leaving a logical name "FOO" behind so
>that if it is run before the INST_*.t tests, they fail as they are trying
>to create a file named "FOO".
>
>When you use the MMS script to run the tests, they are run in a subprocess
>so this is not noticed.

Yes, there are a lot of logical name vulnerabilities.





Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>