On Fri, Nov 06, 2015 at 04:26:26PM +0100, Martin Kolman wrote: > On a related note - what about the screen/spoke naming ? > The original idea was just to use the Anaconda spoke class names, > but maybe some generic naming should be used ? Anaconda is going to be the baseline for the new API so I think we should just use our class names. If a spoke sets multiple items it will note that in that spoke's section of the file. > Maybe one additional issue - should the folder be called "anaconda" or > maybe as something neutral, such as "installation" or os_installation" > ? I'm asking because according to Michaels email, it might happen that > some tools would be writing to the file even before Anaconda is > started. No need for a new directory in there, just a file named anaconda should be fine. -- Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT) _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
