Sandro Tosi <[email protected]> writes: > On Mon, Jan 23, 2012 at 22:06, Russ Allbery <[email protected]> wrote:
>> python-futures for the package name, surely, no? > do you mean the binary? that will be python-concurrent.futures, as per > python policy; for the source I'm open to comments I was thinking of the source. If you're building a single binary package from the source package, it's usually better for everyone's level of confusion to just name the source package the same as the binary package. But my main point was just to avoid having a source package named "futures"; that's a little general. :) -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
