were I designing a package system I'd probably put in a field in a package's metadata for "notable packages that depend on this one" because splitting up a package into smaller packages is mostly great but then the discoverability sucks
You make me feel vindicated for ASDF's support for "secondary systems" in a same build file, as well as the ability to have multiple build files in a repository, each with its own "primary system" and secondary systems. OTOH, the facility to search for systems was never great.
-
-
I've seen some discussion of adding something like that to Cabal. In the process of adding module mixins, they added support for defining multiple build units in a single cabal project - it's just currently only possible make a single one of them 'public'.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!