[Pkg-gdb-logs] [gdb] 01/01: Add *even more* stuff to README.python_switch

[Samuel Bronson]

This is an automated email from the git hooks/post-receive script.

naesten-guest pushed a commit to branch master
in repository gdb.

commit 89ffd1f8b87a0aea020bfb06a944e27649546fe2
Author: Samuel Bronson <naesten at gmail.com>
Date:   Thu Aug 28 03:34:24 2014 -0400

    Add *even more* stuff to README.python_switch
    
    Git-Dch: Ignore
---
 debian/README.python_switch | 33 ++++++++++++++++++++++++++++-----
 1 file changed, 28 insertions(+), 5 deletions(-)

diff --git a/debian/README.python_switch b/debian/README.python_switch
index 4be2291..fae28b6 100644
--- a/debian/README.python_switch
+++ b/debian/README.python_switch
@@ -1,5 +1,7 @@
 # -*- mode: org; -*-
 
+#+STARTUP: showall
+
 For jessie, GDB uses Python 3 by default.
 
 * Users
@@ -47,11 +49,22 @@ For jessie, GDB uses Python 3 by default.
 
 * Packagers
 
-  Packages will be considered *buggy* if their GDB scripts do not work
-  with both Python 2 and Python 3.
+  - Packages will be considered *buggy* if their GDB scripts do not
+    work with *both* Python 2 *and* Python 3.
+
+    + This is partly so that things will work for users of both gdb and
+      gdb-python2, and partly because it is the only sane way to do
+      things upstream: GDB can only be built with one version of Python
+      at a time, and not all distributions, users, etc. have/are/will
+      switch(ed/ing/) at the same time (or even in the same direction).
+
+  - Packages will be considered *RC buggy* if they conflict with,
+    break, or depend on either gdb or gdb-python2 just because of such
+    broken scripts.
 
-  Packages will be considered *RC buggy* if they conflict with, break,
-  or depend on either gdb or gdb-python2 just because of such scripts.
+    + It is, after all, better to have scripts that don't work than to
+      be unable to even install the package it is in.  Also, users
+      could have other builds of GDB around to use such scripts with.
 
   The "six" module may be useful for reference/inspiration here:
     <https://pythonhosted.org/six/>
@@ -60,5 +73,15 @@ For jessie, GDB uses Python 3 by default.
     <http://docs.pythonsprints.com/python3_porting/py-porting.html>
 
   If you would like us to make each gdb package pull in the
-  appropriate "six" module, we would be happy to do that; just file a
+  appropriate "six" package, we would be happy to do that; just file a
   bug and/or prod SamB on IRC.
+
+  - The motivation being to prevent lib or -dbg packages (wherever you
+    ship you scripts) needing to either reinvent pieces of the "six"
+    package or pull in python-six *and* python3-six (thus keeping both
+    versions of python installed) when the user may not even have or
+    want to use gdb: there *are* other uses for -dbg packagse, and
+    some scripts are shipped in lib packages anyway.
+
+  - However, this probably won't be too helpful from an upstream PoV
+    unless we can get this to happen on other distros as well.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gdb/gdb.git