Ahmad Khalifa <ahmad@khalifa.ws> writes:
- github.com/olebedev/when - small library, should I ITP for it separately?
+1
- github.com/urfave/cli/v2/altsrc - package
golang-github-urfave-cli-v2-dev exists already, but altsrc package
is specifically excluded from d/rules. How to deal with this? add it
back in? Separate package?
Fork that salsa project, re-add altsrc and try to get it to build, and
then post patches for discussion on the list. Sometimes adding things
is easy, sometimes it ends up getting really complex.
- github.com/stripe/stripe-go - this I'm afraid is beyond my
paygrade. It's massive. Is there a way to exclude stripe from the
source package if I know how to patch it out or is this just
ultimately incompatible until stripe is packaged?
Depends on how important stripe-go is for ntfy -- sometimes you can
patch things out, and sometimes you can strip down the dependent package
into "mini" variant with only the library functions required by ntfy.