On Fri, May 3, 2024 at 5:03 AM Michael Schwendt <mschwendt@xxxxxxxxx> wrote:
On Wed, 1 May 2024 23:10:18 -0400, Jeffrey Walton wrote:
> I was amazed the file project broke the command. The projects I contribute
> to will move mountains to avoid breaking established behavior. We don't
> want to screw our users like that.
In such a case, your script ought to apply some safety measures.
Like putting some guards in front that verify that the printed type for
specific files matches your expectations. It wouldn't take much to maintain
your own small set of input files as an automatic test-suite.
I thought the same thing about the file program. The change should have caused a regression when running its self tests. The authors should have known there was a problem with what they did.
The "file" type output has changed before. And the printed types are better
not parsed as a full sentence but as individual keywords in a set. Your
primary interest seems to be in detecting the term "CSV".
Various scripts that rely on console output have broken before, mistakenly
expecting specific status/error/whatever messages.
Jeff
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
