|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
praiskup commented 2 years ago | ||
|
||
|
||
|
||
|
||
praiskup commented 2 years ago Comment append also resets the value, if it is specified as the first rule. Both "comment" and "comment_append" set the already_modified value. | ||
|
||
frostyx commented 2 years ago Will this append, and append, and append, on each run? if not chroot.comment.endswith(rule["comment_append"]): chroot.comment += rule["comment_append"] | ||
praiskup commented 2 years ago It is not re-appending. That's the purpose of the | ||
frostyx commented 2 years ago I still have doubts. | ||
praiskup commented 2 years ago I think it is fine, take a look above (chroot.comment is always reset before it is appended, for each of the command runs). | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
We have dozens of chroots, and it has been tedious task to configure the
comments for them manually (copy-pasting the long comments, maintaining
links, etc.). The new command automatizes this by applying rules from
a new /etc/copr/chroots.conf configuration file.
The "comment" always re-sets the value.