Hi Clint,
On 15 November 2012 03:53, Clint Byrum cl...@ubuntu.com wrote:
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
On Thu, Nov 15, 2012 at 11:17:40AM +, Thomas Kluyver wrote:
I have been keeping an eye on pkgme, but I'm not sure it solves the
problem. My concern with automated tools is that they tend to to work for
about 75% of stuff, but there's always a substantial proportion of things
that just do
On 15 November 2012 15:18, Andrey Rahmatullin w...@wrar.name wrote:
Bottom line: if you want to get a good package, it's not always possible
to fully automate that, especially in cases of complex (and proprietary)
software like that you mentioned, and so a GUI wizard can't do everything
On Nov 15, 2012, at 04:15 PM, Thomas Kluyver wrote:
- uscan puts upstream tarballs into ../, but svn-buildpackage expects them
in ../tarballs/
- To work on patches, you have the debian/ directory in amongst the
upstream codebase. But having the rest of the codebase there clutters up
information
* Thomas Kluyver tho...@kluyver.me.uk, 2012-11-09, 13:19:
- Do you think this is worth spending time on?
I don't think so, sorry.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 14 November 2012 11:43, Jakub Wilk jw...@debian.org wrote:
I don't think so, sorry.
Could you expand on this at all? Do you think that packaging should be left
to the experts? Or that the existing systems are easy enough for newcomers
to learn?
Thomas
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
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
On Fri, 2012-11-09 at 13:19 +, Thomas Kluyver wrote:
In my opinion, the best way to do that is to build a GUI that holds
the user's hand through the process of packaging, showing them the
options available. It should be particularly useful for occasional
packagers who don't want to
9 matches
Mail list logo
