On Tue, Jul 15, 2025 at 03:22:44PM +0200, Cristian Le via devel wrote: > Hi all, > > During the review of bash-preexec [1] we came up on the issue that according > to the documentation, this package would be in conflict with any other bash > script that use the variable `PROMPT_COMMAND` or `DEBUG` > > > # Note: This module requires two Bash features which you must not > > otherwise be > > # using: the "DEBUG" trap, and the "PROMPT_COMMAND" variable. If you > > override > > # either of these after bash-preexec has been installed it will most > > likely break. > > But how do we enforce this incompatibility? From a talk at last year's > devconf [2], I've learned that you can add a Provides+Conflicts with the > same name which would disallow other packages with the same Provides to be > installed. I am considering using this mechanism. > > My proposal here is to define `Provides: bash(PROMPT_COMMAND)` for this > package, and hopefully other packages that use it and would probably have a > similar restriction. What do yall think?
The 'setup' RPM provides /etc/bashrc & includes logic that sets the PROMPT_COMMAND variable. You can't add a conflicts against the 'setup' RPM as that's installed essentially everywhere, so this approach looks non-viable With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
