[scl.org] Rolling release naming

Brian Gollaher briang at redhat.com
Tue Nov 8 14:51:45 UTC 2016

First question is why do you need a rolling name?  And will it meet the 
general naming requirements for RHSCL?

Naming SCLs was a difficult process that took a few years with lots of 
customer involvement to get right.  My understanding is that there are 
incompatibilities with node.js releases that may cause a yum update to 
break user apps.  Is that correct?


On 11/08/2016 09:40 AM, Zuzana Svetlikova wrote:
> Currently, we chose the name of the collection by the version
> of the software we're packaging (rh-python35, sclo-php56 etc).
> I'd like to have a collection, that would be "rolling release"
> and for that reason I cannot use the version naming (nodejs
> releases major version every ~6 months).
> I could use something like sclo-nodejs-current, but that would
> result in terribly long package names that I'd like to avoid.
> Does anyone have any good ideas how to name such collection?
> Thanks
> Zuzka
> _______________________________________________
> SCLorg mailing list
> SCLorg at redhat.com
> https://www.redhat.com/mailman/listinfo/sclorg

Brian Gollaher
Red Hat Platform Product Management
Phone: 978 392-3173
Cell: 508 740-6549
briang at redhat.com

More information about the SCLorg mailing list