From 8f22d3c1fffe8c9414ace60a6b14a8904f86d875 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Thu, 6 Apr 2023 21:02:03 +0000 Subject: config: describe order dependency in cgitrc parsing I just had to do a double-take here and look back at cgit.c to see the ordering dependency wasn't a bug I introduced, but mimicking what cgit does. --- lib/PublicInbox/Config.pm | 2 ++ 1 file changed, 2 insertions(+) (limited to 'lib/PublicInbox/Config.pm') diff --git a/lib/PublicInbox/Config.pm b/lib/PublicInbox/Config.pm index e095ecd1..df488f23 100644 --- a/lib/PublicInbox/Config.pm +++ b/lib/PublicInbox/Config.pm @@ -318,6 +318,8 @@ sub parse_cgitrc { $k =~ tr/-/_/; $self->{"-cgit_$k"} = $v; } elsif (m!\Ascan-path=(.+)\z!) { + # this depends on being after project-list in the + # config file, just like cgit.c if (defined(my $list = $self->{-cgit_project_list})) { scan_projects_coderepo($self, $list, $1); } else { -- cgit v1.2.3-24-ge0c7