.make.log files in subdirectories sometimes not created
Status: Beta
Brought to you by:
worden
Menu
▾
▴
#314 .make.log files in subdirectories sometimes not created
When making a target in a subdirectory of the project directory, if make is responsible for creating the subdirectory, WW will fail to write into a .make.log file, because it will fail to create it in a directory that doesn't exist yet. Maybe I should put .make.log files somewhere else? It would also be nice to not add clutter in the working directory.
Related
Discussion
Anonymous
There is a .workingwiki/ directory in each project now, where .d files go. I could put .make.log files there, in which case I could make sure they always have their parent directory so this problem won't happen.
But carefully - people have pages that expect .make.log files to be where they are now, so moving them could be destructive.
Would it be a problem to start locating .make.log files in the .workingwiki/ directory, out of sight of casual browsing?
The only downside I can think of is that existing pages display .make.log files using filenames that would stop working.
I don't think there are any make rules that involve processing a .make.log into something else...
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Processing the .make.log into something else is explicitly deprecated, at least in our discussions. I like this idea. I'm also wondering if we could solve most of the transition problems with a clever make rule.
The question "what about subdirectories?" would still need to be addressed.
That was me just now!
Which questions about it?
If we put .make.log files in .workingwiki/, I can create e.g. .workingwiki/subdir/subdir-file.make.log reliably by making sure .workingwiki/subdir is created before I run make. Whereas in the main working directory I don't want to create the directory before running make, because I want to leave make alone so that it runs the same in the wiki as outside it.
Well the question was "what to do about files in subdirectories"? Your answer sounds good.
My ideas for not breaking things don't work: we don't want to make make logs, and even if we did, the existing pages all say make=false, so there's no way not to break them.
I would say to go ahead and break them, and let people fix them, with the caveat that when you make something you should look for and delete its legacy .make.log. Can't have old wrong ones sitting around being displayed.
Yes. I guess I could also replace legacy make logs with something that
links to the new make log? Though I guess not in a very elegant way
because it's a plain text file