Bug 984932

Oh, and system-config-keyboard:

Traceback (most recent call last):
  File "/usr/sbin/firstboot", line 30, in <module>
    import firstboot.frontend
  File "/usr/lib/python2.7/site-packages/firstboot/frontend.py", line 30, in <module>
    from system_config_keyboard import keyboard
ImportError: No module named system_config_keyboard

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

The firstboot utility is deprecated and no longer developed in Fedora 19 and newer releases. It was replaced by the initial-setup utility with a completely different codebase. If you still have any similar problems with Fedora 19 or later, please file a new bug against initial-setup or gnome-initial-setup if you did a GNOME install.

But initial-setup has no documentation or examples for how to produce a module such as the firstboot module I'm using. 

So as far as I was concerned, it *wasn't* a viable replacement. I'd even gone to the trouble of porting my module's UI to gtk3, but ended up switching back again and using firstboot even for Fedora 19.

There's been *talk* about producing documentation and standalone examples for initial-setup, but none of that was available last time I looked. There is no example for how to do stuff and ensure that it appears and works correctly in initial-setup/gnome-initial-setup etc.

(In reply to David Woodhouse from comment #4)
> But initial-setup has no documentation or examples for how to produce a
> module such as the firstboot module I'm using. 
> 
> So as far as I was concerned, it *wasn't* a viable replacement. I'd even
> gone to the trouble of porting my module's UI to gtk3, but ended up
> switching back again and using firstboot even for Fedora 19.
> 
> There's been *talk* about producing documentation and standalone examples
> for initial-setup, but none of that was available last time I looked. There
> is no example for how to do stuff and ensure that it appears and works
> correctly in initial-setup/gnome-initial-setup etc.
As far as the initial-setup goes, there is a way to produce a module it can load and run -- write an anaconda addon. Because the initial-setup uses anaconda's UI code internally. Please have a look at the development guide I started writing a while ago (and unfortunately haven't had enough time to finish since then) [1] and a the hello world addon example refered from there. Also, you may find useful having a look at the addon I did as part of my masters thesis [2].

Creating an addon for the Initial Setup is just a matter of inheriting one special mixin class that lives in the anaconda's codebase. I'll be more than glad to help you with these things.

[1] http://vpodzime.fedorapeople.org/anaconda-addon-development-guide/
[2] https://fedorahosted.org/oscap-anaconda-addon/

May I suggest moving further communication about the addon development to emails or IRC? You can reach me at the #anaconda channel on FreeNode. I hope I'll find some time to finish the guide ASAP.