Hi, * Andreas Tille <andr...@an3as.eu> [2024-02-28 11:51]:
I think it could be useful for the routine-update command to stop when such file is hit, in order to raise the importance that the package has quirks, and should not be casually updated without involved scrutiny. I wonder whether this can be generalized, like if d/README.source file is present? (Although the latter use is codified[2] and I'm not confident it is 100% suitable for such purpose: I see many such files on my radar which do not necessarily hint for quirks.)
I like all your suggestions. When reading Timo's suggestion about debian/README.DPT I also thought about rather using the more generic debian/README.source. In any case I agree that routine-update should respect such debian/README.* (except debian/README.Debian which is user oriented).
I also thought of README.source at first, and I remained on the fence until Étienne brought up the potential use for routine-update, which makes me think that a dedicated "quirks" file makes more sense. I'm not too attached to the .DPT suffix though, maybe something like README.team or even README.quirks signals the intention behind the file even better. I'll leave the bikeshedding to interested readers for now. :)
Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature
