• Skip to sidebar navigation
  • Skip to content

Bitbucket

  • More
    ProjectsRepositories
  • Help
    • Online help
    • Learn Git
    • Welcome to Bitbucket
    • Keyboard shortcuts
  • Log In
Alexander Dahl
  1. Alexander Dahl

buildroot

Public
Actions
  • Clone
  • Compare

Learn more about cloning repositories

You have read-only access

Navigation
  • Source
  • Commits
  • Branches
  • All Branches Graph
  • Forks
  1. Alexander Dahl
  2. buildroot

Source

buildroot/Config.in.legacy
Carlos SantosCarlos Santos committed 6c10e40d23922 Oct 2017
Raw file
Source viewDiff to previous
# Note: BR2_PACKAGE_LVM2_DMSETUP_ONLY is still referenced in package/lvm2/Config.in
 
1
#
2
# Config.in.legacy - support for backward compatibility
3
#
4
# When an existing Config.in symbol is removed, it should be added again in
5
# this file, and take appropriate action to approximate backward compatibility.
6
# This will make the transition for the user more convenient.
7
#
8
# When adding legacy symbols to this file, add them to the front. The oldest
9
# symbols will be removed again after about two years.
10
#
11
# The symbol should be copied as-is from the place where it was previously
12
# defined, but the help text should be removed or replaced with something that
13
# explains how to fix it.
14
#
15
# For bool options, the old symbol should select BR2_LEGACY, so that the user
16
# is informed at build-time about selected legacy options.
17
# If there is an equivalent (set of) new symbols, these should be select'ed by
18
# the old symbol for backwards compatibility.
19
# It is not possible to select an option that is part of a choice. In that
20
# case, the new option should use the old symbol as default. This requires a
21
# change outside of Config.in.legacy, and this should be clearly marked as such
22
# in a comment, so that removal of legacy options also include the removal of
23
# these external references.
24
#
25
# [Example: renaming a bool option that is part of a choice from FOO to BAR]
26
# original choice:
27
#   choice
28
#       prompt "Choose foobar"
29
#   config BR2_FOO_1
30
#       bool "foobar 1"
31
#   config BR2_FOO_2
32
#       bool "foobar 2"
33
#   endchoice
34
#
35
# becomes:
36
#   choice
37
#       prompt "Choose foobar"
38
#       default BR2_BAR_1 if BR2_FOO_1 # legacy
39
#       default BR2_BAR_2 if BR2_FOO_2 # legacy
40
#   config BR2_BAR_1
41
#       bool "foobar 1"
42
#   config BR2_BAR_2
43
#       bool "foobar 2"
44
#   endchoice
45
#
46
# and in Config.in.legacy:
47
#   config BR2_FOO_1
48
#       bool "foobar 1 has been renamed"
49
#       help
50
#         <suitable help text>
51
#   # Note: BR2_FOO_1 is still referenced from package/foo/Config.in
52
#   config BR2_FOO_2
53
#       bool "foobar 2 has been renamed"
54
#       help
55
#         <suitable help text>
56
#   # Note: BR2_FOO_2 is still referenced from package/foo/Config.in
57
#
58
# [End of example]
59
#
60
# For string options, it is not possible to directly select another symbol. In
61
# this case, a hidden wrap bool option has to be added, that defaults to y if
62
# the old string is not set at its default value. The wrap symbol should select
63
# BR2_LEGACY.
64
# If the original symbol has been renamed, the new symbol should use the value
65
# of the old symbol as default. Like for choice options, a comment should be
66
# added to flag that the symbol is still used in another file.
67
#
68
# [Example: renaming a string option from FOO to BAR]
69
# original symbol:
70
#   config BR2_FOO_STRING
71
#       string "Some foo string"
72
#
73
# becomes:
74
#   config BR2_BAR_STRING
75
#       string "Some bar string"
76
#       default BR2_FOO_STRING if BR2_FOO_STRING != ""  # legacy
77
#
78
# and in Config.in.legacy:
79
#   config BR2_FOO_STRING
80
#       string "The foo string has been renamed"
81
#       help
82
#         <suitable help text>
83
#
84
#   config BR2_FOO_STRING_WRAP
85
#       bool
86
#       default y if BR2_FOO_STRING != ""
87
#       select BR2_LEGACY
88
#
89
#   # Note: BR2_FOO_STRING is still referenced from package/foo/Config.in
90
#
91
# [End of example]
92
​
  • Git repository management for enterprise teams powered by Atlassian Bitbucket
  • Atlassian Bitbucket v6.7.2
  • Documentation
  • Request a feature
  • About
  • Contact Atlassian
Atlassian

Everything looks good. We'll let you know here if there's anything you should know about.