Re: Notifying post-install tools about screens seen by the user

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 05, 2015 at 09:11:16AM -0800, Brian C. Lane wrote:
> On Thu, Nov 05, 2015 at 04:59:07PM +0100, Martin Kolman wrote:
> > 
> > Looking forward to your feedback! :)
> 
> Some random thoughts:
> 
> Ideally we wouldn't have to do this. The other apps should be able to
> detect when something has been changed from the default and skip it.

The goal should be to skip the screen if the user previously visited a
similar or the same screen.  But visiting a screen doesn't mean they made a
change.  All of those UX aspects aren't really recorded in setting the
timezone for the system.  I agree that other apps should skip it if the
default has been changed, but we don't record the default anywhere.  Maybe
that's how we record the state change.

> Synchronizing this configuration file between anaconda and the other
> apps means that any changes we make will need to be coordinated.

True, this would now be a public API.  But that's not necessarily a bad
thing.

> Will the entries in the file be translated? I'd suggest they be in
> English.

I don't think translation is important here since it's a config file that
users don't ever have to look at.

> /etc/sysconfig/anaconda or /etc/default/anaconda seems like a better
> place for this than a whole new directory in /etc/

I like either of these ideas.  That file could also carry more UX
information if we need to in the future.

> Visiting a spoke isn't the same as changing something. I think we should
> base this on changes, shouldn't we?

I think so.

> I almost like the idea of parsing the kickstart better, it is already a
> known well defined format, we already write it out, and it wouldn't
> require coordinating a new thing with everyone.

The downside to that is that we'd start overloading kickstart with UX
metadata, which seems unnecessary.  That and the parser for it is Python
only, which would make it difficult for programs like g-i-s.  I think we can
probably do this with VARIABLE=VALUE syntax in a /etc/sysconfig/anaconda
file.

-- 
David Cantrell <dcantrell@xxxxxxxxxx>
Manager, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list



[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux