这是indexloc提供的服务,不要输入任何密码
Skip to content

keep build state when running command again #23840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

john-peterson
Copy link
Contributor

flag -f will rerun configure but the source and build folders are never
deleted. it is necessary for testing that it behaves like a manual build .
usually many runs are required before everything succeed

@fornwall can you intervene here. I also speak Swedish and is also a
theoretical physicist PhD currently hiking the mountains of Tasmania.
@thunder-coding is not as experienced as us but is closing good commits
left and right without any understand of how anything works

flag -f will rerun configure but the source and build folders are never
deleted. it is necessary for testing that it behaves like a manual build .
usually many runs are required before everything succeed

@fornwall can you intervene here. I also speak Swedish and is also a
theoretical physicist PhD currently hiking the mountains of Tasmania.
@thunder-coding is not as experienced as us but is closing good commits
left and right without any understand of how anything works
@robertkirkman
Copy link
Contributor

It is a helpful idea, however, very unfortunately, if you run this command after applying this PR,

scripts/run-docker.sh ./build-package.sh -I -a all docbook-xml

this will happen:

replace docbook-xml-4.1.2/calstblx.dtd? [y]es, [n]o, [A]ll, [N]one, [r]ename: 

Do you know how to do this without causing something like that to happen?

@robertkirkman
Copy link
Contributor

Additionally, there is very unfortunately another situation where a similar problem happens, but only when this PR is applied, and not with the current way that is in the repository.

scripts/run-docker.sh ./build-package.sh -I -a all groovy
mv: cannot stat 'jansi-jansi-2.4.1': No such file or directory

Is it possible to make this be an optional setting that has to be turned on, instead of editing an existing default setting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants