Building in non-initialized project without explicit parameter #482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #472
Now, it is possible to build packages without using any parameters.
To silence the warnings, it is possible to use the
--without-init
parameterIf the
.tito
directory exists, the--without-init
parameter does nothing. So when integrating into Copr, the--wihout-init
parameter can be used every time for every project. But maybe we should rename it to--ignore-missing-init
,--ignore-missing-config
,--ignore-init-warnings
, or something like that?One more thing that I realized is that we can only build in non-initialized projects when using
--test
. Without it, we getWe will need that for Copr, right @praiskup?