Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncm-*: Migrate remaining yes/no strings to legacy_binary_affirmation_string type #752

Closed
jrha opened this issue Apr 12, 2016 · 1 comment
Assignees
Milestone

Comments

@jrha
Copy link
Member

jrha commented Apr 12, 2016

As discussed in #749, there are several components that use a similar string but defined directly as a string and match rather than a type, e.g.

'create_home' ? string with match (SELF,'yes|no')

These should be migrated to legacy_binary_affirmation_string.

@jrha jrha added this to the 16.4 milestone Apr 12, 2016
@jrha jrha changed the title ncm-*: ncm-*: Migrate remaining yes/no strings to legacy_binary_affirmation_string Apr 12, 2016
@jrha jrha changed the title ncm-*: Migrate remaining yes/no strings to legacy_binary_affirmation_string ncm-*: Migrate remaining yes/no strings to legacy_binary_affirmation_string type Apr 12, 2016
@jrha
Copy link
Member Author

jrha commented Apr 12, 2016

Components/culprits include:

  • ncm-accounts
  • ncm-afsclt
  • ncm-cups
  • ncm-iptables
  • ncm-nscd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant