Hi Dmitry, On Sun, 10 Feb 2019 16:21:04 +0300, Dmitry Monakhov wrote: > Read QUILT_PC from config instead of using hardcoded one.
We never documented QUILT_PC as being user-changeable, but sure, why not. The test suite does not cover it but it should work. Makes me curious... Are you actually changing QUILT_PC, and if so, why? > Do it as we do with QUILT_PATCHES var. This is reasonable, however I'm worried by 2 implementation details: 1* We read from ~/.quiltrc only. This is only one of three possible sources for QUILT_PATCHES (/etc/quilt.quiltrc and .pc/.quilt_patches are the other two), and one of two possible sources for QUILT_PC (/etc/quilt.quiltrc is the other one). Ideally the search logic should be the same as the one used internally by quilt. 2* The functions do not cache the result, so the expensive processing will be done over and over again, even though the result will be the same every time. And this is going to get worse if we fix issue #1 above. These problems are not added by your patch, they were present before already, but your patch aggravates them, so it might be the right time to look into them. I can't help though, not using emacs at all. I wonder if it could help to add a pseudo-command (helper) to quilt itself? Something like "quilt getenv QUILT_PATCHES" which would return what quilt-patches-directory is currently returning, and same for QUILT_PC to replace function quilt-pc-directory? It would be more expensive than doing it manually, however this would guarantee that the results match. If the result is cached then the extra cost should no longer be an issue. -- Jean Delvare SUSE L3 Support _______________________________________________ Quilt-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/quilt-dev
