How should packages for Blue Quartz products be named ?
The original packages had names like the following:
Qube3-All-Kernel-4.0.1-2.2.16C37-III-1.pkg
RaQ550-All-Kernel-0.0.1-2.4.19C13_V-1.pkg
Or some cryptic Sun Cobalt internal bug numbering...
I know that BlueLinQ (just like RPM) doesn't care
about the name of the PKG file, but looks inside
the package for the product build (5100WG/5100R).
But should the packages really be named:
BlueQuartzWorkgroupEdition-All-Name-version-release.pkg
BlueQuartzHostingEdition-All-Name-version-release.pkg
Or can we agree on something a little snappier perhaps ? :-)
(preferably without "Qube", "3", "RaQ" and "550" as those
are all potential trademark conflicts with Sun Cobalt...)
--anders