I never did get used to running make on my config files.
Or the pain of somebody on the team routinely editing the output files without making the changes on the config files, and never knowing whether it'll work the same when you're done.
> I never did get used to running make on my config files.
I worked in a very Make oriented place. If you need to do any processing on files, which not only includes compiling them, but also pushing them to other servers, and loading them into memory on those servers, that should be done with Make. Because Make makes things :)
Now I'd rather write a Makefile than use whatever language's builder of the week. Make can make things, why do I need anything else?
Shudders. The LPIC exams I took back in 2005 made me think I would spend the next 20 years in vim manually configuring apache, sendmail, bind, openldap and a bunch of other stuff I haven't touched since the exam.
doubled112|3 years ago
Or the pain of somebody on the team routinely editing the output files without making the changes on the config files, and never knowing whether it'll work the same when you're done.
toast0|3 years ago
I worked in a very Make oriented place. If you need to do any processing on files, which not only includes compiling them, but also pushing them to other servers, and loading them into memory on those servers, that should be done with Make. Because Make makes things :)
Now I'd rather write a Makefile than use whatever language's builder of the week. Make can make things, why do I need anything else?
jbverschoor|3 years ago
raffraffraff|3 years ago