On 3/10/2015 12:57 AM, "Greg Troxel" <gdt%ir.bbn.com@localhost> wrote:
>
>
> David Sainty <david.sainty%gmail.com@localhost> writes:
>
> > On 02/10/15 11:45, Greg Troxel wrote:
> > GCC_REQD
> >
> > A list of values specifying the minimum version of the GNU Compiler
> > Collection that is required to build this package. The list is
> > constructed from version numbers appended by this package and by any
> > included buildlink3.mk files. Each package or buildlink3.mk file will
> > generally append at most a single version number to GCC_REQD; forming
> > a list of version numbers of which the maximum version is the
> > definitive one.
>
> Can we say "each package sets exactly one"? If it's "the mininum", more
> doesn't make sense.
The reason why I didn't disallow more than one is that I can imagine a package using conditional logic where it's easier to just add a new version to the list than it is to go to the effort of ensuring one and only one version is added by each package.
I didn't want to prohibit it in documentation when it would otherwise be perfectly legal.
But I am trying to hint that more than one would be odd. Would you be happy with a stronger hint? :)
> And, I'm not totally comfortable with this because it gives up on the
> incompatible versions above minimum notion.
Oh, that's not my intention, I'm just trying to improve the current documentation at this stage to reduce confusion over what the current unmodified code does. It's all subject to change :)