Consistent configuration/example files installation#2704
Conversation
|
The first thing is is fully intentional. encoding_profiles.conf is actually parsed on loading, and actually contains active settings. The other conf files are fully documented and are just examples. The second commit would be acceptable, though. |
|
I would avoid installing files directly to I have a hidden agenda with this issue: in OpenBSD all files in packages are checksumed, so we can't install to |
|
@czarkoff do |
|
Not really. When called during |
|
Well it's not like most users would edit config files directly in the Otherwise how do other OpenBSD ports handle system wide config files? A lot (most?) of software out there installs default config files to |
|
Most software doesn't use waf. This is not real code, but things like that work with GNU and BSD makefiles, simple configure scripts, cmake lists, auto*-generated makefiles and everything else I ever dealt with. |
|
Yeah, most software uses cmake these days, or MSVC+Xcode project files. |
|
@wm4 I see increasing amounts of pure makefile-based configuration. In my experience, these are easiest to write, most readable and far more flexible. |
|
So you want the 10kloc shell vomit back that mplayer had? |
|
@wm4 I sort of liked |
|
And 1500 lines of old-* don't look as bad as 53967 lines of waf. |
Because it supported only desktop Linux (and maybe OpenBSD if you hacked it a bit). |
|
I have no clue about building software on OSX, but MinGW support would not double that number. Assuming that nothing from old build system is reusable on OSX, there is still about 50k lines of overhead with waf. And making waf handle unit tests in adequate fashion would add yet more overhead. |
Some packagers need to install config files to a different path but still load from another path. See #2704
|
^ that should fix your problem, hopefully |
|
Yes, it helps. What about another commit ( |
|
I dropped the |
|
Looks ok, will apply later. (Maybe you could add "etc: " as prefix, but I can do that myself.) |
|
Pushed that commit. |
Some packagers need to install default config files to some path but automatically load system configuration files from another path. See #2704
2 participants
While not really issues, these are inconsistencies that I find irritating:
encoding_profiles.conftoCONFDIR, but other installation files are installed intoDOCDIR.example.confis a filename formpv.confexample. Other examples' names are the same with configuration files they are examples of.