[bug #62595] Add ability to read .env files into make

Update of bug #62595 (project make): Summary: Add ability to read .env files into make and => Add ability to read .env files into make ___ Reply to this item at:

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #8, bug #62595 (project make): > Of course you can also use the re-exec feature of make to write a rule to generate the include file then you have the full power of a recipe. I like the idea, especially because of the re-exec feature. However, my goal was to avoid having to make

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #7, bug #62595 (project make): Thanks for the pointer to the spec, that's very helpful. I agree that this would be possible to implement. I'm not interested in a flag like --envfile, that doesn't sound very useful. I would anticipate that most build systems would want to

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #6, bug #62595 (project make): > ⚠ External Email > > Follow-up Comment #4, bug #62595 (project make): > > No, no, that's not something one should expect from a .env file. > > I said that _some_ dotenv parsers take it a step further to do all that fancy >

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #5, bug #62595 (project make): I'd never heard of these env file things, so appreciated the well-written posts that those links point to. Why would this feature be better in Make rather than in a wrapper? If you wanted, for some reason that I'm struggling to guess, to keep

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #4, bug #62595 (project make): No, no, that's not something one should expect from a .env file. I said that _some_ dotenv parsers take it a step further to do all that fancy interpolation, but really .env files are just files containing a bunch of key=value lines, no functions

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #3, bug #62595 (project make): Right, so that's just a shell script that doesn't happen to do anything except set variables. Your comment 'The format of a .env file is simply "key=value"' is not the case, as you yourself point out when you say "the single quotes surrounding the

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #2, bug #62595 (project make): Hi Paul .env files are commonly used for specifying secrets for an application or a build. Please see this question to get an idea of how people are currently trying to use .env files in their Makefile:

[bug #62595] Add ability to read .env files into make and

Follow-up Comment #1, bug #62595 (project make): I don't know what an ".env" file is. Do you mean, a shell script? It's not possible to embed a shell parser into make. Or, I guess it would be possible but it's not something I think is a good idea. If you don't mean a shell script, is there

[bug #62595] Add ability to read .env files into make and

URL: Summary: Add ability to read .env files into make and Project: make Submitter: firstairbender Submitted: Wed 08 Jun 2022 03:43:10 AM CDT Severity: 3 - Normal