Package: wnpp
Severity: wishlist
Owner: Michael Fladischer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: mockldap
Version : 0.1.4
Upstream Author : Peter Sagerson
* URL : http://bitbucket.org/psagers/mockldap/
* License : BSD
Programming L
Svante Signell writes:
> On Tue, 2013-11-26 at 00:16 -0600, Steve Langasek wrote:
>> The only way to address the Essential conflict for the jessie release
>> seems to be to move the contents of sysvinit to a new package, and make
>> sysvinit a metapackage that depends on an ORed list of the possi
On 11/26/2013 04:19 PM, Russ Allbery wrote:
> Svante Signell writes:
>> On Tue, 2013-11-26 at 00:16 -0600, Steve Langasek wrote:
>
>>> The only way to address the Essential conflict for the jessie release
>>> seems to be to move the contents of sysvinit to a new package, and make
>>> sysvinit a m
On 26 November 2013 10:42, Thomas Goirand wrote:
> On 11/26/2013 04:19 PM, Russ Allbery wrote:
>> Svante Signell writes:
>>> On Tue, 2013-11-26 at 00:16 -0600, Steve Langasek wrote:
>>
The only way to address the Essential conflict for the jessie release
seems to be to move the contents
Package: wnpp
Severity: wishlist
Owner: Olivier Berger
* Package name: python-django-ldapdb
Version : 0.2.0
Upstream Author : Jeremy Laine
* URL : https://github.com/jlaine/django-ldapdb
* License : BSD
Programming Lang: Python
Description : An LDAP da
On Tue, Nov 26, 2013 at 06:42:43PM +0800, Thomas Goirand wrote:
> This is correct, OpenRC uses sysvinit, and replaces only sysv-rc
> (which BTW shows that replacing a well working PID 1, or adding any
> piece of code in it, is absolutely not needed at all)
...to achieve what OpenRC achieves.
--
Package: wnpp
Severity: wishlist
Owner: Zygmunt Krynicki
* Package name: plainbox
Version : 0.4
Upstream Author : Zygmunt Krynicki
* URL : https://launchpad.net/checkbox/
* License : GLP
Programming Lang: Python
Description : toolkit for software and h
Package: wnpp
Severity: wishlist
Owner: Paul Tagliamonte
* Package name: docker.io
Version : 0.6.x or 0.7.x depending on how lazy I am
Upstream Author : dotCloud
* URL : http://docker.io
* License : apache2
Programming Lang: Go
Description : easy contai
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting
* Package name: libcgi-struct-xs-perl
Version : 1.04
Upstream Author : Dmitry Smal
* URL : https://metacpan.org/release/CGI-Struct-XS
* License : BSD-2-clause
Programming Lang: Perl / XS
Descriptio
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting
* Package name: libcpanel-json-xs-perl
Version : 2.3403
Upstream Author : Reini Urban
* URL : https://metacpan.org/release/Cpanel-JSON-XS
* License : same as Perl
Programming Lang: Perl / XS
Descri
Package: wnpp
Severity: wishlist
Owner: Florian Schlichting
* Package name: libjson-maybexs-perl
Version : 1.00
Upstream Author : Matt S. Trout
* URL : http://search.cpan.org/dist/JSON-MaybeXS/
* License : GPL-1+, Artistic
Programming Lang: Perl
Descri
Hello list and Joey,
about a year ago, I reported a wishlist bug on debconf (#690390, more
details below). I received a reply which seemed to say you agree with
me on all points except implementation. I asked why you didn't agree on
that, since it would make many things better, IMO. Unfortunate
Bas Wijnen wrote:
> Currently, many packages only do 2
(Citation needed.)
> packages should implement parsing code for it in its config script. My
> point is that this results in needless code duplication. Therefore I
> would like to move this parsing code to debconf
I'd think it would be obviou
Op 27-11-13 02:44, Joey Hess schreef:
> Bas Wijnen wrote:
>> Currently, many packages only do 2
>
> (Citation needed.)
>
>> packages should implement parsing code for it in its config script. My
>> point is that this results in needless code duplication. Therefore I
>> would like to move this par
Bas Wijnen writes:
> What this means, is that every package which asks debconf questions (and
> stores the answers in a configuration file) will need to:
> 1. Parse the configuration file, if it exists, and set the values as
> defaults before asking the questions. (in the config script)
> 2. Upd
On Tue, Nov 26, 2013 at 09:44:40PM -0400, Joey Hess wrote:
> Bas Wijnen wrote:
> > Currently, many packages only do 2
>
> (Citation needed.)
http://codesearch.debian.net/search?q=db_get+path%3A.*config%24
On Tue, Nov 26, 2013 at 06:16:19PM -0800, Russ Allbery wrote:
> > Currently, many packages
Bas Wijnen writes:
> Certainly. You seem to have misunderstood my intention. I don't mean
> to say we should force packages to use a standard package.config. That
> file should be used to do all the things it must do. What I'm proposing
> is to make it easy for packages with simple file forma
Bas Wijnen wrote:
> > (Citation needed.)
>
> http://codesearch.debian.net/search?q=db_get+path%3A.*config%24
If the presence of db_get in a config script was always a bug, then I
[cw]oud modify debconf to not allow db_get in config scripts.
But, it's not. Randomly reviewing only packages I have
If someone would really like to improve the state of debconf use in
config scripts, I think that the best approach would be to find a way
to replace the current imperative config scripts with a declarative
format.
--
see shy jo, fan of applicative functors, though sometimes you gotta
2013/11/27 Joey Hess :
> I'd think it would be obvious why it's not good design to put parsers
> for every possible config file format in debconf.
There is libaugeas.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
20 matches
Mail list logo
