BIE Package Name

[lmkennethburnett]

Currently there is a BIE package version name, but not a name for the package itself. The system currently allows multiple packages with the same package version name and package version id. This can make it harder to identify a correct package programmatically without knowing the internal package id.

Should the package have a unique name, either added to or more likely in place of the package version name, such that the version identifiers belong under that package name? This would be more like package management systems with name/version id combinations uniquely identifying the package.

[hakjuoh]

The reason we didn’t introduce a uniqueness check for the combination of Package Version Name and Version ID was because we thought it might be unnecessary from a usability perspective, such as allowing for potential duplicates just in case. But do you think we should implement it? Could you please let us know if there are any cases in which having multiple packages with the same Package Version Name and Version ID is needed?

[lmkennethburnett]

I can't think of a situation where duplicates would be wanted, and the existence of duplicates can cause problems, so I think we shouldn't allow it. Is the Package Version Name essentially the same thing as a Package Name?

[lmkennethburnett]

The Package Version Name was apparently meant as a sort of version title and not as the package name. Based on the BIE Package component development discussions, adding a separate, unique package name to connectCenter would be appropriate. It might be useful to have all of the versions of a package name underneath it instead of in a flat list of combinations. I think it would still be useful to disallow duplicates of a version name and id within the same package name.