Bug#863118: devscripts needs proper configuration file parsing

[CC-ing Xavier in case he has missed this conversation] > * 0016-Move-all-parsing-of-configuration-files-to-a-separat.patch (and let-uscan-use-confvar.patch) Devscripts::Confvar answers the needs of all 25 existing Perl or Shell scripts. For each one, I have checked that settings in

Bug#863118: devscripts needs proper configuration file parsing

Hi, On Sun, Nov 04, 2018 at 02:46:43PM +0100, Nicolas Boulenguez wrote: > Patches 1 to 15 carry various non intrusive suggestions improving > details, but not specific to Confvar. About those, thank you! I've applied most of them here my comments about some: *

Bug#863118: devscripts needs proper configuration file parsing

Package: devscripts Version: 2.18.7 Followup-For: Bug #863118 Hello. Since last message, most sources have been reformatted. uscan.pl has been heavily modified, introducing a new Devscripts::Config library similar to Devscripts::Confvar. The attachment rebases all previous patches in this

Bug#863118: devscripts needs proper configuration file parsing

Package: devscripts Followup-For: Bug #863118 Hi. Please also consider these two patches. Thanks. >From a97cd3da68e8abeb1d3d3cf52bc66e092c0ed3d3 Mon Sep 17 00:00:00 2001 From: Nicolas Boulenguez Date: Fri, 23 Feb 2018 10:28:27 +0100 Subject: [PATCH 1/2] Clean pylint

Bug#863118: devscripts needs proper configuration file parsing

Package: devscripts Followup-For: Bug #863118 Please ignore previous attachment, and consider this one instead. It brings various improvements, including tests. It also splits the unrelated changes in order to ease review. Thanks. devscripts_confvar.tar.gz Description: application/gzip

Bug#863118: devscripts needs proper configuration file parsing

Package: devscripts Followup-For: Bug #863118 Control: tags -1 + patch Hi. The attached changes fix this bug. They are intrusive and probably introduce new bugs, but they should ease the maintenance in the long run. Regards. suggestions.tar.gz Description: application/gzip

Bug#863118: devscripts needs proper configuration file parsing

On Sun, Jun 04, 2017 at 10:21:39AM +0900, Osamu Aoki wrote: > Hi, > > On Sat, Jun 03, 2017 at 01:45:36PM -0400, James McCoy wrote: > > On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote: > > > OK, here is my try to do the following. Ugly, yes. But it seems to > > > catch most errors in

Bug#863118: devscripts needs proper configuration file parsing

Hi, On Sat, Jun 03, 2017 at 01:45:36PM -0400, James McCoy wrote: > On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote: > > OK, here is my try to do the following. Ugly, yes. But it seems to > > catch most errors in friendly way. > > > > * "egrep" test to catch space after "=" > > *

Bug#863118: devscripts needs proper configuration file parsing

On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote: > OK, here is my try to do the following. Ugly, yes. But it seems to > catch most errors in friendly way. > > * "egrep" test to catch space after "=" > * "set -e" to detect command not found; >* space before "=" >* "false"

Bug#863118: devscripts needs proper configuration file parsing

control: tags -1 patch > > > This is a hack, not a proper handling of the configuration. > > > > fwiw, the maintainers have been in violent agreement with this for years, > > but it needs someone with tuits to replace the current situation with a > > solution that's usable from all the languages

Bug#863118: devscripts needs proper configuration file parsing

On Mon, May 22, 2017 at 09:36:37AM +0100, Adam D. Barratt wrote: > On 2017-05-22 9:14, Adrian Bunk wrote: > > devscripts.conf(5) says: > > > > The two configuration files are /etc/devscripts.conf for system-wide > > defaults and ~/.devscripts for per-user settings. They are written > > with

Bug#863118: devscripts needs proper configuration file parsing

On 2017-05-22 9:14, Adrian Bunk wrote: devscripts.conf(5) says: The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written with bash(1) syntax, but should only have comments and simple variable assignments in

Bug#863118: devscripts needs proper configuration file parsing

Package: devscripts Version: 2.17.5 Severity: normal devscripts.conf(5) says: The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written with bash(1) syntax, but should only have comments and simple variable