Hi, On Friday, 28 November 2025 at 04:15:33 pm IST, Cristian Le via devel wrote: On 2025/11/28 11:32, Prasad Pandit wrote: > A common case is an multi-user environment like when ssh-ing to a server > where you might not know that the package is installed. Having a way to > make these more opt-in in a per-user case would be useful.
* ccache(1) allows to define user specific CCACHE_DIR, in case system CCACHE is not accessible, no? I might be missing some details/background here, but new sub-package to disable ccache(1) globally does not seem right. System-level enabling/disabling and access scope of ccahe(1) is already handled by CCACHE_DIRs and other environment/configuration options upstream. >If we can eliminate the need for such a package, that would be ideal. * True. >But how do we make it more out-of-the-box experience for the users? * Maybe we can set some default system-wide options in /etc/ccache.conf ? > One thing I was considering was somehow making these as systemd > user/system service to add to the `~/.bashrc.d` directory, > but that would be just another thing to teach since we can't enable > it by default for the user right? It would at least eliminate the > need for a dedicated sub-package since it could be toggled on-off > via systemctl instead. * What are we trying to solve/address really? Are we looking to disable system-wide ccache(/var/cache/ccache/) access by default? Thank you. --- -Prasad -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
