Conversation
|
I've revised the suggested documentation to refer Cabal's users to GHC's boot package |
|
Thanks, this is looking much better. I made some more suggestions; please apply as you see fit, although I would like to avoid the "system semaphore" terminology as I will open an MR against |
Wow, I realise there were a lot of bugs with the Haddocks in v2 of |
|
I have put up |
This has been merged and the documentation is available online on Hackage. Please let me know if there is anything else you would like to see documented. |
This is follows GHC's dependency on `semaphore-compat-2.0.0` (first reflected in GHC 9.12.5-rc2). The terminology of the dependency package now: * introduces the concept of protocol versions for semaphores (there remains only one protocol version on Windows); * distinguishes server semaphores and corresponding client semaphores; and * distinguishes unversioned client semaphore names and client semaphore identifiers. This conforms the language in Cabal's User Guide to that of the package.
EDIT: To be clear, this is only about documenting Cabal (the library) under
runhaskell Setup.hs buildand not about the executable provided by thecabal-installpackage.This is follows GHC's dependency on
semaphore-compat-2.0.0(first reflected in GHC 9.12.5-rc2).The terminology of the dependency package now:
This conforms the language in Cabal's User Guide to that of the package.
This PR does not modify behaviour or interface