On Fri, Mar 16, 2018 at 4:04 PM, Dennis Gregorovic <dgregor@xxxxxxxxxx> wrote:
The challenge here is that those module builds are squeezed into a N-V-R format when imported into Koji. The N-V-R format is used for all build types in Koji and it works well for its purpose, but it's also not realistic to expect that all content types are going to natively use N-V-R outside of Koji. My suggestion is that we consider the N-V-R format of modules to be a representation internal to koji and that N:S:V:C is the format used to represent modules to users. If that means tweaking the Koji UI we can look into that.
There's also a terminology problem that gets less confusing with the : separator. When compared to
Name-VERSION-Release.DistTag
it would be fairly confusing to have:
Name-Stream-VERSION.Context
while:
Name:Stream:VERSION:Contextis slightly less confusing. of course, it might have been better to call 'Version' in a module version Build or something, but I think that ship has sailed.
In the end, modules are not packages, and it's necessarily required or good if they are named in the same format. I'd also like to see Koji's representation of a module version stay inside Koji as much as possible.
Owen
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
