[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#677115: marked as done (per-subcommand config file sections)

Your message dated Wed, 11 Dec 2024 18:28:11 +0000
with message-id <[🔎] E1tLRRT-00ByeE-6O@fasolo.debian.org>
and subject line Bug#1088867: Removed package(s) from unstable
has caused the Debian Bug report #677115,
regarding per-subcommand config file sections
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
677115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677115
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: python-cliapp
Version: 0.29-1
Severity: wishlist

Hello,

I'm hitting a limit in the default "command line options in config file"
behaviour: I have a "--output" option that sends the command output to a
file instead of stdout.

I'd like to set a config file option to avoid typing this command:

  egt backup --output="/var/backups/egt-%Y-%m-%d-%H:%M:%S.tar"

but I still want this command to send output to stdout:

  egt weekly-report


A possible implementation would be allowing a per-subcommand section in
the config file, like this:

  [cmd backup]
  output = "/var/backups/egt-%Y-%m-%d-%H:%M:%S.tar"

the section being ignored unless the given subcommand is being run.

I didn't suggest to just use [backup] for the section name, because
that would be ambiguous if one implemented a 'config' subcommand.
However, 'cmd ' looks rather ugly, and just the subcommand name would
feel much more natural. An alternative, backwards-compatible strategy
could be to also accept something like "[DEFAULTS]" for the main
section, and if the main section is named that way then 'config' is not
treated specially and can be used for subcommands.

Unfortunately ConfigParser won't parse a config file with data outside
of any section header: that would have been a perfect solution to the
ambiguity.

However, it does accept "[ ]" (must have a space) as a section header.
It's another option, but still not so natural.


Ciao,

Enrico

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-cliapp depends on:
ii  python     2.7.2-10
ii  python2.6  2.6.7-4
ii  python2.7  2.7.3~rc2-2.1

python-cliapp recommends no packages.

Versions of packages python-cliapp suggests:
ii  libjs-query       <none>
ii  libjs-underscore  1.1.6-1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1.20180812.1-7+rm

Dear submitter,

as the package python-cliapp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1088867

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: