Closed hmogensen closed 3 years ago
Thanks for trying out RDM!
We'll have to look into this further, but it seems like a problem with the data/history.yml
file that contains the development history for your project.
To start, lets just comment out these lines:
https://github.com/innolitics/rdm/blob/master/rdm/init_files/Makefile#L29-L31
and also delete this file:
https://github.com/innolitics/rdm/blob/master/rdm/init_files/documents/release_history.md
Then see if everything works. If so, then we can look into what's going on with the history.yml file generation.
Thanks a lot for your quick reply. With your adjustments, the make command executes without error. I will rename this issue to be only about the history.yml file generation, and maybe I will open a new one about adding features from my sample project.
I haven't dived too deep in the reason for the above error. However, funny thing is I could not reproduce the error after importing your project to Gitlab and redoing the setup (on the same computer). The error occurs when I clone a project to a subfolder in the regulatory folder, and update the config.yml file as described in the first post. The only second error I still had this time was something with the mkdir command, instead of interpreting the -p flag as a setting the command interprets it as the name of a folder. Thus it creates a folder named release
and a folder named -p
for the first document, and for the second document it throws an error because the folder it tries to create already exists. This is probably a Windows idiosyncrasy, if I was more familiar with bash scripting I would provide a quick solution to this problem for you but now I just comment out these lines and create the folder manually.
I haven't dived too deep in the reason for the above error. However, funny thing is I could not reproduce the error after importing your project to Gitlab and redoing the setup (on the same computer). The error occurs when I clone a project to a subfolder in the regulatory folder, and update the config.yml file as described in the first post. The only second error I still had this time was something with the mkdir command, instead of interpreting the -p flag as a setting the command interprets it as the name of a folder. Thus it creates a folder named
release
and a folder named-p
for the first document, and for the second document it throws an error because the folder it tries to create already exists. This is probably a Windows idiosyncrasy, if I was more familiar with bash scripting I would provide a quick solution to this problem for you but now I just comment out these lines and create the folder manually.
Regarding the issue with the -p directory, it has to do with your environment you use for make. Out of the box, you cannot run the Makefile in windows. I tried a variety of different consoles and settled on git-bash, with a manual installation of make. This combination let me run the Makefile successfully, since it supported all the commands.
I am trying out your software on a dummy project
The documentation and the code standard of your project is awesome, however I have a couple of problems with the history.yml file generation. I am running Windows 10 Enterprise (x64),, with make installed with Chocolatey Python3.8
I do the following steps (in Anaconda console)
rdm init
cd regulatory
git clone https://github.com/hmogensen/my-sample-project
make
Output:
If I rerun
make
, only one file from the documents folder will be processed unless I comment out the commands@mkdir -p $(@D)
in the Makefile, since the script tries creating a new folder each time. After having performed this modification, running make yields the following output: