Excerpts from Thomas Kluyver's message of 2012-11-09 05:19:03 -0800: > This is an idea I've had knocking around for a while. Packaging is complex > - there are lots of different tools and syntaxes you have to understand to > do a good job of it - quilt, debhelper, watch files, etc. - along with > specialist terminology. I know various CLI tools aim to simplify things, > but not everything can be automated, and the tools end up with lots of > options to learn about. > > The upshot is that most open source developers rely on a relatively small > number of specialist packagers to do the rather esoteric work of preparing > Debian packages. To get this to scale, I think we need to encourage more > upstreams to provide packaging - whether it's for inclusion in Debian, or > to provide .deb packages themselves, like Google Chrome, MongoDB and > Dropbox do.
As part of the effort to encourage development of Applications for Ubuntu, pkgme was created. The idea was to generate *full packages* based only on the usual metadata provided to most build systems or language-specific packaging systems. https://launchpad.net/pkgme At one point I was interested in writing a ruby backend for this, but got distracted and moved to other focus, but I think it solves what you are talking about, without need to develop a large project like a GUI. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1352951434-sup-8...@fewbar.com