At 2026-01-27T21:31:42+0000, Deri wrote: > On Tuesday, 27 January 2026 21:09:37 GMT G. Branden Robinson wrote: > > "Inline::C creates a work directory in your home directory called > > "_Inline", if you would prefer it used somewhere else then set > > environment variable PERL_INLINE_DIRECTORY to a writeable directory." > > > > Is this a commonplace convention in the Perl community, or something > > you innovated for gropdf? [...] > The Inline man page says:- > > ========================================================================= > The Inline ’directory’ > Inline needs a place to build your code and to install the results > of the build. It uses a single directory named '.Inline/' under > normal circumstances. If you create this directory in your home di‐ > rectory, the current directory or in the directory where your pro‐ > gram resides, Inline will find and use it. You can also specify it > in the environment variable "PERL_INLINE_DIRECTORY" or directly in > your program, by using the "directory" keyword option. If Inline > cannot find the directory in any of these places it will create a > '_Inline/' directory in either your current directory or the direc‐ > tory where your script resides. > ========================================================================== > > I could embed ~/.Inline in the code if that is considered better.
I personally think so, as it's more consistent with my expectations as a Unix user of, uhh, over 30 years now.[1] Even dot files and directories got numerous and cluttery over the years, so people came up with the XDG Base Directory specification. https://specifications.freedesktop.org/basedir/latest/ But if Perl itself hasn't yet adopted that spec, I reckon it would be better to stick with their default. What do other folks on the list think? Regards, Branden [1] I can _feel_ my hair graying when I say things like that.
signature.asc
Description: PGP signature
