On Aug 31, 2015, at 10:44 AM, Jay McCarthy <[email protected]> wrote:
> On Mon, Aug 31, 2015 at 10:42 AM, Jon Zeppieri <[email protected]> wrote: >> My reasoning went like this: >> >> - As far as I know, no one is using this library. (But, if anyone is, >> please let me know.) >> - It's actually extremely unlikely that the changes would break any >> existing code, even if the library were being used. (But, if I have >> broken your code, again, please let me know.) > > IMHO, being able to think like this is a feature of the package > system. Compatibility/etc is not a technical question but a social one > and we'd like ways of easily providing the technical details and forum > for that conversation to take place. I can imagine ways it could be > better, like a tool that helps authors tell how and where their code > was used. This wouldn't completely solve that problem, but it would go part way: Would it be possible to get a list of all of the packages that declare a dependency on a certain package? It should be; I think the pkg-dep-draw package does something similar. -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/10918BD7-6621-4C51-97AB-986B44F5D141%40knauth.org. For more options, visit https://groups.google.com/d/optout.
