You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the :bt nickname given to binary-types conflicts with the nickname given to bordeaux-threads ... and while this isn't exactly a bug, it does prevent (for example) cl-inotify from loading in any system that also uses bordeaux-threads. Is it possible to drop/change the nickname assigned to the binary-types package?
The text was updated successfully, but these errors were encountered:
I must say I haven't really done anything with binary-types for ..
years. I don't even know which (if any) download location you're
thinking of. Feel free to chance the nickname any way you see fit.
Regards,
Frode Fjeld
On Fri, Jan 27, 2012 at 10:22 PM, Brian O'Reily [email protected]
wrote:
I noticed that the :bt nickname given to binary-types conflicts with the nickname given to bordeaux-threads ... and while this isn't exactly a bug, it does prevent (for example) cl-inotify from loading in any system that also uses bordeaux-threads. Is it possible to drop/change the nickname assigned to the binary-types package?
Reply to this email directly or view it on GitHub: #1
Thanks for the response, Frode. When I went looking for who to talk to about the nickname issue, I got the impression that the package may be an archeological artifact, but it is still in use, notably in the cl-inotify package, and it appears that it can be cloned from your github account. :) If you want, I can issue a pull req with an updated nickname tag.
I noticed that the :bt nickname given to binary-types conflicts with the nickname given to bordeaux-threads ... and while this isn't exactly a bug, it does prevent (for example) cl-inotify from loading in any system that also uses bordeaux-threads. Is it possible to drop/change the nickname assigned to the binary-types package?
The text was updated successfully, but these errors were encountered: