<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en" style='--code-editor-font: var(--default-mono-font, "GitLab Mono"), JetBrains Mono, Menlo, DejaVu Sans Mono, Liberation Mono, Consolas, Ubuntu Mono, Courier New, andale mono, lucida console, monospace;'>
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style data-premailer="ignore" type="text/css">
a { color: #1068bf; }
</style>
<style>img {
max-width: 100%; height: auto;
}
body {
font-size: .875rem;
}
body {
-webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px;
}
body {
font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji"; font-size: inherit;
}
</style>
</head>
<body style='font-size: inherit; -webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px; font-family: "GitLab Sans",-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji";'>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.com/adrien-n">adrien</a>
<a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1849#note_2005282207">commented</a>:
</p>
<div class="md" style="color: #28272d; word-wrap: break-word;">
<p dir="auto" style="color: #28272d; margin: 0 0 16px;" align="initial">I think file and directory should both be usable at the same time. That being said, in my quick experiment on yesterday, I made it so that the directory one is disabled by default in configure.ac but that's also something I'm very hesitant about and entirely open to change (default would be /etc/gnutls/config.d and it's unlikely that there's already something else there).</p>
<p dir="auto" style="color: #28272d; margin: 0 0 16px;" align="initial">Multiple configurations would be treated exactly the same way as if they were concatenated together with <code style='font-size: 90%; color: #18171d; word-wrap: break-word; background-color: #ececef; border-radius: .25rem; margin-top: 0; font-weight: inherit; font-family: "GitLab Mono","JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; white-space: pre-wrap; overflow-wrap: break-word; word-break: keep-all; padding: 2px 4px;'>cat</code>. I think the current implementation with a single file does not treat repeated keys in a specific manner and this wouldn't change. The implementation would simply read all files one after the other, using the same context. I've found that <code style='font-size: 90%; color: #18171d; word-wrap: break-word; background-color: #ececef; border-radius: .25rem; font-weight: inherit; font-family: "GitLab Mono","JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; white-space: pre-wrap; overflow-wrap: break-word; word-break: keep-all; padding: 2px 4px;'>inih</code> makes this approach very easy and natural. I'd like to make the testsuite reflect that: prove single-file and split-files configuration are read the same.</p>
<p dir="auto" style="color: #28272d; margin: 0 0 16px;" align="initial">This approach has the benefit of not changing the semantics: configuration lines are simply spread over several files. It is possible to introduce inconsistencies and using several files makes this slightly easier because the user may only look at a single file but I believe the scope in gnutls is small enough (a few lines at most) that this won't matter in practice.</p>
<p dir="auto" style="color: #28272d; margin: 0;" align="initial">My main scenario for this is to allow users to customize their distribution's configuration. That user can do that either manually or by running a tool but in both cases, the affected files do not overlap the ones from the distribution's packages. This is also applies if the main file configuration is empty but a tool manages some files in the configuration directory.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #737278;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1849#note_2005282207">view it on GitLab</a>.
<br>
You're receiving this email because of your account on <a target="_blank" rel="noopener noreferrer" href="https://gitlab.com">gitlab.com</a>. <a href="https://gitlab.com/-/sent_notifications/6bdf638ada21e6d46f2a12d0793a2ebd/unsubscribe" target="_blank" rel="noopener noreferrer">Unsubscribe</a> from this thread · <a href="https://gitlab.com/-/profile/notifications" target="_blank" rel="noopener noreferrer" class="mng-notif-link">Manage all notifications</a> · <a href="https://gitlab.com/help" target="_blank" rel="noopener noreferrer" class="help-link">Help</a>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/-/merge_requests/1849#note_2005282207"}}</script>
</p>
</div>
</body>
</html>