Dear list,
I am having a hard time finding documentation about the best way to make
locally installed software recognize its config dir in
/usr/local/etc/xdg. Of course, the quick and easy answer could be:
$ env XDG_CONFIG_DIRS=/usr/local/etc/xdg foobar
But that is not something one can ask
S or it needs to be set an compile time. I
would very much prefer the first option and want to know, if that is
possible or even intended.
> > On Sep 16, 2021, at 12:44 AM, Peter White wrote:
> >
> > Dear list,
> >
> > I am having a hard time finding documentation
On Thu, Sep 16, 2021 at 04:15:07PM +, Bollinger, John C wrote:
> The value of XDG_CONFIG_DIRS, if set, is expected to be a string
> designating one or more directories to search for config files, in
> priority order. If multiple directories are specified then they are
> separated by colon
On Thu, Sep 16, 2021 at 11:39:30AM -0400, Elsie Hupp wrote:
> > XDG_CONFIG_DIRS acts like PATH does: first match wins, which
> > I would not expect to happen with conffiles.
>
> In general I believe the expectation is for the XDG variables with the
> plural suffix (i.e. ending in “S”) to return
On Sun, Sep 19, 2021 at 12:19:33PM +0200, David Faure wrote:
> On jeudi 16 septembre 2021 18:48:41 CEST Peter White wrote:
> > But, /etc should be off limits for software in /usr/local, right?
>
> I don't think this assessment is correct.
>
> For instance, I certainl
On Thu, Sep 16, 2021 at 01:21:15PM -0400, Elsie Hupp wrote:
> >>> I have pondered this for a while now and could also not find
> >>> anything via search engine or on this list, so I figured I actually
> >>> ask the ones who wrote the spec.
> >>
> >> I did not write the spec, but I have
On Thu, Sep 16, 2021 at 02:49:40PM +, Bollinger, John C wrote:
> Your concerns seem to be focused mostly on how to deal with having
> multiple versions of the same application installed simultaneously.
Exactly.
> The challenges involved in making that work for applications that rely
> on XDG
On Thu, Sep 16, 2021 at 01:47:51PM -0400, Elsie Hupp wrote:
> >>> I was hoping they would be, or is there a better way of contacting them?
> >>
> >> The authors all have individual email addresses at the top of the
> >> specification:
> >
> > I did notice that, but why ask them privately?
Dear John,
would you please reply on the list, it being the only recipient? By
putting me first, I don't get the list headers cannot do a proper list
reply.
On Thu, Sep 16, 2021 at 05:38:37PM +, Bollinger, John C wrote:
> Dear Peter,
>
> What XDG Base Directory does not particularly
On Mon, Sep 20, 2021 at 10:20:05AM +0200, David Faure wrote:
> On dimanche 19 septembre 2021 16:57:22 CEST Peter White wrote:
> > On Sun, Sep 19, 2021 at 12:19:33PM +0200, David Faure wrote:
> > > On jeudi 16 septembre 2021 18:48:41 CEST Peter White wrote:
> > > >
On Mon, Sep 20, 2021 at 08:50:45AM -0400, Elsie Hupp wrote:
> > The way you describe it, it would be OK for any app to just parse the
> > config of any other. That just feels wrong, because app A should have no
> > business snooping in /etc/xdg/B/Brc. If app B wants to make such
> > information
On Mon, Sep 20, 2021 at 02:09:00PM +, Bollinger, John C wrote:
> So what are you looking for at this point, Peter? I think we're well
> past any question of interpreting the details of the spec, and we've
> even delved a bit into its history and design goals and its intended
> usage model.
On Mon, Sep 20, 2021 at 09:46:22AM -0400, Elsie Hupp wrote:
> > Yes, and then there is XDG which expects exactly that, which
> > then leads to other hacks to soften the isolation of said
> > containers, or the inclusion of files which the go out of
> > sync and out of date compared to what is in
On Mon, Sep 20, 2021 at 03:28:09PM +0100, Simon McVittie wrote:
> On Mon, 20 Sep 2021 at 12:28:43 +0000, Peter White wrote:
> > Why would XDG_CONFIG_DIRS need to contain ${PREFIX}/etc/xdg for that?
> > The app pretty much already knows where it is supposed to find *its own*
> &g
On Mon, Sep 20, 2021 at 03:06:06PM +0100, Simon McVittie wrote:
> On Thu, 16 Sep 2021 at 04:44:17 +0000, Peter White wrote:
> > I am having a hard time finding documentation about the best way to make
> > locally installed software recognize its config dir in
> > /usr/local/e
On Mon, Sep 20, 2021 at 03:04:39PM -0400, Elsie Hupp wrote:
> Mr. White,
>
> You write:
>
> > Be that as it may, one should not have to resort to such rather
> > extreme measures just to get sane behaviour back. And please stop
> > drumming for Flatpak. It does have its application but not for
Correction, sorry I just noticed:
On Mon, Sep 20, 2021 at 11:49:31PM +, Peter White wrote:
> 2. Read in reverse order, so as to go from least important to most
-> important, files in XDG_CONFIG_HOME, if it is set, move on otherwise.
+> important, files in XDG_CONFIG_DIRS, if it is
On Mon, Sep 20, 2021 at 05:37:02PM -0400, Eli Schwartz wrote:
> On 9/20/21 12:03, Peter White wrote:
> > The way I see it there will be two universes: FHS and a subtly different
> > XDG Base Dir Spec, which breaks with the former in peculiar subtle ways
> > and any d
On Mon, Sep 20, 2021 at 06:14:49PM -0400, Elsie Hupp wrote:
> > I find it intriguing that you insult people
> > right back by calling an *extremely* common convention in technical
> > mailing lists, a "dusty cultural artifact" and suggesting that it is
> > malicious behavior.
>
> I’ve been using
19 matches
Mail list logo
