I'd like to split kf5-qt5-build-include into three files (frameworks, workspace, applications), and to keep kf5-qt5-build-include as the file that includes the other three.
But if my kdesrc-buildrc says
and that file says
then kdesrc-build is looking for that file in the current directory, not in the extragear/utils/kdesrc-build directory.
Could include files with a relative path be considered relative to the file including it? Maybe with a "./" syntax if the current semantics have to be kept, but I doubt that?
Steps to Reproduce:
1. cd extragear/utils/kdesrc-build
2. wget http://www.davidfaure.fr/2013/0001-split-up-kf5-qt5-build-include.patch
3. git am 0001-split-up-kf5-qt5-build-include.patch
4. cd ../../..
Config error: Unable to open file ./kf5-frameworks-build-include which was included from line 1
Can't continue, so stopping now.
Git commit 83a91b98c3148bdf3b181eb093c7c45020a9157d by Michael Pyne.
Committed on 02/01/2014 at 05:23.
Pushed by mpyne into branch 'master'.
Make relative include entries relative to their own rc-file.
As opposed to making them relative to script location, original rc-file,
initial cwd, or similar. This allows for whole directory trees to be
moved around if need be as well as long as the internal links remain
I've tested this on a sample here and also on the provided test case
with the bug and it seems to work well although I have not had time to
run through a whole build, merely the --pretend sequence.
M +2 -1 modules/ksb/Application.pm
M +41 -0 modules/ksb/RecursiveFH.pm