Some general points before I wade in next week: - I'm sympathetic to the idea that packaging a JavaScript project in Python as its (supposedly?) primary distribution mechanism is odd. I'm happy to try to find some alternatives, as Maris proposed.
- Maris says that our build tools have value for us in Launchpad. * If we in Launchpad are the only ones using them because they are weird and no one else wants them for some reason, let's move them in the Launchpad tree and make them easier for us to use and change by making them less general. Maybe we can also try to learn why the tools we built are not useful externally, so we can do better next time, either by starting projects only in Launchpad, or by doing a better job with the tools we want to share. * On the other hand, if other teams do use them, we can figure out what the right packaging is on the basis of who else is using them. We'll prefer sdists, but it would be easy to provide a PPA as well. I'd love for this to be a very quick job, and I'll strongly prefer expedient solutions that unblock(?) Paul, perhaps with an clean-up task for us to schedule later. If you all agree on an expedient solution while I'm out, great. :-) Gary _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
