-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
To be more precise, most tools accept files ending in ".conf". We might want tor to accept ".conf" for consistency.
I suggest we also accept files called "torrc", or ending in ".torrc". This should probably also include files called literally ".torrc".
Thank you for your suggestions, teor! I have updated it in the ticket.
Since this is a breaking change, we might want to check if any distribution has adopted another naming scheme, and avoid breaking that naming schem
I agree. I will wait for a little bit before implementing it so that we may get more input on the issue. :)
If you'd like your patch to be reviewed quickly: * put the ticket in 0.3.3, because it's a bugfix * change the status to "needs review" once you have a patch
Thank you so much for your instructions!
Best Regards, iry
On 5 Feb 2018, at 08:09, iry iry@riseup.net wrote:
Since this is a breaking change, we might want to check if any distribution has adopted another naming scheme, and avoid breaking that naming schem
I agree. I will wait for a little bit before implementing it so that we may get more input on the issue. :)
Expecting packagers to follow every thread and reply here is unrealistic.
Would you mind doing the search yourself, like Patrick asked? It seems to have dropped off your TODO list.
Could you please look at existing .d folders of any other projects tell me what you think? Perhaps discuss this with Tor Project.
https://forums.whonix.org/t/torrc-d-is-comming/4041/13
From my quick search, it appears that the Debian feature request is still open, and no other distro is using torrc.d yet. But you should check, too.
T