Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
bugzilla
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
etersoft
bugzilla
Commits
082cea0b
Commit
082cea0b
authored
May 01, 2014
by
Dave Miller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug 999296: make checksetup.pl not complain about having added new
values to localconfig when the answers were supplied by an answer file. r=LpSolit, a=justdave
parent
7c6963dd
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
2 deletions
+8
-2
Localconfig.pm
Bugzilla/Install/Localconfig.pm
+8
-2
No files found.
Bugzilla/Install/Localconfig.pm
View file @
082cea0b
...
...
@@ -222,14 +222,20 @@ sub update_localconfig {
# a 256-character string for site_wide_secret.
$value
=
undef
if
(
$name
eq
'site_wide_secret'
and
defined
$value
and
length
(
$value
)
==
256
);
if
(
!
defined
$value
)
{
push
(
@new_vars
,
$name
);
$var
->
{
default
}
=
&
{
$var
->
{
default
}}
if
ref
(
$var
->
{
default
})
eq
'CODE'
;
if
(
exists
$answer
->
{
$name
})
{
$localconfig
->
{
$name
}
=
$answer
->
{
$name
};
}
else
{
# If the user did not supply an answers file, then they get
# notified about every variable that gets added. If there was
# an answer file, then we don't notify about site_wide_secret
# because we assume the intent was to auto-generate it anyway.
if
(
!
scalar
(
keys
%
$answer
)
||
$name
ne
'site_wide_secret'
)
{
push
(
@new_vars
,
$name
);
}
$localconfig
->
{
$name
}
=
$var
->
{
default
};
}
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment