Hi, Michal has asked me about a case where /etc/YaST2/ProductFeatures is missing, and I didn't know, started looking, and still don't know. What actually is ProductFeatures? Where do the values come from? How is it different from ProductControl? Where is/should_be this doumented? I looked in https://github.com/yast/yast-yast2/tree/master/library/control/src/modules http://www.rubydoc.info/github/yast/yast-yast2/Yast/ProductFeaturesClass http://www.rubydoc.info/github/yast/yast-yast2/Yast/ProductControlClass -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On 9.1.2014 10:29, Martin Vidner wrote:
Hi,
Michal has asked me about a case where /etc/YaST2/ProductFeatures is missing, and I didn't know, started looking, and still don't know.
What actually is ProductFeatures? Where do the values come from? How is it different from ProductControl? Where is/should_be this doumented?
IIRC, product features are generated from control file some time during the installation. Which might not be there if you build it as an appliance (and thus not install). On the other hand, I usually get the info directly from control file using ProductControl and I don't care about ProductFeatures at all. The truth is that ProductFeatures might be a bit faster than ProductControl as it doesn't need to parse XML. You might grep Yast for ProductFeatures - maybe it's something to drop / replace with ProductControl. Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Lukas Ocilka -
Martin Vidner