[Info-vax] OpenSSL 1.1.0 released

[Craig A. Berry]

On Tuesday, September 6, 2016 at 9:33:42 AM UTC-5, Richard Levitte wrote:
> Den tisdag 6 september 2016 kl. 16:27:26 UTC+2 skrev Stephen Hoffman:
> > On 2016-09-06 11:40:38 +0000, Richard Levitte said:
> > 
> > > No, that didn't quite work...  BUT, you did put me on the right path 
> > > here, 'cause this seems to work the way I want:
> > 
> > I'm getting the impression that the following diagnostic means that the 
> > parser and/or the scanner may well have lost its way:
> > 
> > %PCSI-I-MULOBJ, the file {filespec} is multiply defined; conflict 
> > resolution may occur on installation
> > 
> > The PCSI filename parser has already had problems with lowercase and 
> > with <>, so another oddity is certainly not out of the realm of 
> > possibility.
> > 
> > IOW: the above diagnostic looks like it might really be an error, not 
> > an informational.
> 
> It is quirky in this regard for sure...

Quirky, but documented.  There is a little more info in the v8.4 on-line help under PRODUCT PACKAGE/MATERIAL than there was in in the 7.3-2 era docs I cited earlier:

=======

When the path-name contains a root directory, the utility appends
the relative file specification from the FILE statement in the
PDF to the root directory to determine where to find the file.
However, when either a specific directory or a wildcard directory
is used in the path-name, the relative file specification from
the FILE statement is not used to find the file. Instead, the
directory as specified in the /MATERIAL qualifier is used to
search for the file.

Note that when you use either a wildcard directory or a list of
path names, if files in different directories have the same name,
only the first file in the search path is packaged in the kit.
As a result, the same file is packaged each time a FILE statement
refers to the file name because the relative file specification
is not used to identify the file uniquely. Therefore, if your
product has different files with the same name in different
directories, you must use the root directory form of the path-
name to package these files correctly.

=======

To me the moral of the story is "always use a rooted directory for value of the /MATERIAL qualifier."  I've done that, but I think it was more by accident rather than knowing that I needed to.