* Arno Töll <a...@debian.org>, 2013-02-02, 21:43:
it would be good, if dput-ng utilites will respect ~/.devscripts
options. For example "export DEBSIGN_KEYID=....", like debsign does.
we cannot easily support ~/.devscripts because that's a sourced shell
fragment.
Actually .devscripts syntax is a strict subset of shell syntax, which
was designed to be easily parsable by software not written in shell.
(For example, many devscripts programs are written in Perl).
Here's what a comment of /etc/devscripts.conf reads:
# This file is sourced by /bin/bash, and should only contain
# comment lines (beginning with a '#'), and lines of the form
# VARIABLE=value
# The value must be quoted if there are spaces in it.
# Variables corresponding to switches (on/off; yes/no) must take
# one of the values 'yes' or 'no'.
# The variable names are all of the form PROGNAME_VARNAME,
# or DEVSCRIPTS_VARNAME if they are more generally applicable.
It's somewhat unfeasible to interpret and parse that in a
third party Python
If you wanted, you could easily parse it with the shlex module.
script which is not (directly) related to devscripts.
Now, this is a real reason not to parse this file. dput-ng is not a part
of devscripts, so it has no business it reading devscripts'
configuration file.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
