Re: [PATCH 1/2] Don't populate flags.cmdline with "True" values when no = is used.

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

 



On Wed, 2009-04-29 at 15:44 -0400, Peter Jones wrote:
> Since all tests are either flags.cmdline.has_key() or "if
> flags.cmdline.get()", we want this to be None when there's no equals
> sign, rather than True.

This breaks at least 'debug' as a boot time option.  The flags dict is
setting {'debug': None} and so later in gui.py or others tests for
"flags.debug" are coming out as false.  I haven't finished checking all
of the other flags that we stuff in to the flags dict, and that are not
foo=bar flags, but there is potential for more breakage here.

What were you trying to fix here?

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
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