Control: tags -1 + pending
Hi
On Wed, Oct 11, 2017 at 11:07:11AM +0200, Salvatore Bonaccorso wrote:
> Hi Klee
>
> Is it still planned to package iniparser for Debian?
>
> I know another small Projekt which I likely will use which depends on
> iniparser, so I wonder if uploading for Debian is s
Hi Klee
Is it still planned to package iniparser for Debian?
I know another small Projekt which I likely will use which depends on
iniparser, so I wonder if uploading for Debian is still planned.
Regards,
Salvatore
On 18/05/14 00:40, Klee Dienes wrote:
> On May 17, 2014, at 3:19 PM, Daniel Lintott wrote:
>> I've taken a look at your packaging at agree it looks good. I noted a
>> couple of things that I've picked up since I started packaging…
>
> Thanks for the feedback! I took most of your suggestions (com
On May 17, 2014, at 3:19 PM, Daniel Lintott wrote:
> I've taken a look at your packaging at agree it looks good. I noted a
> couple of things that I've picked up since I started packaging…
Thanks for the feedback! I took most of your suggestions (comments to follow):
> debian/rules
> - no need
Thanks for the prompt reply!
On 17/05/14 00:05, Klee Dienes wrote:
> You can find my packaged sources at https://github.com/kdienes/iniparser .
I've taken a look at your packaging at agree it looks good. I noted a
couple of things that I've picked up since I started packaging...
debian/rules
-
On May 16, 2014, at 4:43 PM, Daniel Lintott wrote:
> Could I ask what the current situation with iniparser is?
You can find my packaged sources at https://github.com/kdienes/iniparser .
I think they’re ready to upload. I’m currently working my way through the N-M
process, after which I will l
Could I ask what the current situation with iniparser is?
A package I shall be preparing currently depends on iniparser.
Regards
--
Daniel Lintott
GPG Key: 4096R/5D73EC6E
signature.asc
Description: OpenPGP digital signature
On Thu, Feb 13, 2014 at 9:12 PM, Klee Dienes wrote:
> Regarding #2, my goal is to package the psmoveapi code for Debian,
> which uses the write support of iniparser (not supported by inih). I
> also note that Samba seems to include an internal version of
> iniParser.
Please report any embedded c
That’s interesting regarding krb5 … I should have remembered it would have an
INI file parser, but didn’t realize it had write support.
As far as I can tell libconfuse is read-only.
I definitely appreciate the pointers. I have no opinion on 1), but definitely
agree with your point 2).
--
To
The krb5 libraries include read and write support for the krb5.conf
format, which is very similar but not identical to ini.
I would be entirely happy with the response that:
1) the krb5 profile library should be used only for modifying Kerberos
configs
2) supporting the ABI that your application
On Feb 13, 2014, at 8:48 AM, Andrew Shadura wrote:
> Well, we've just removed libmcs which did support writing ini files...
> Is there really nothing else in archive already to support writing
> them?
Thanks for the pointer and for the question.
A quick scan turned up the following C-ish option
Hello,
On 13 February 2014 14:12, Klee Dienes wrote:
> The iniParser library is a simple C library offering INI file parsing
> services (both reading and writing).
> 2) Complexity ("Does anything depend on this, any potential users that
> couldn't use something simpler?")
> Regarding #2, m
Package: wnpp
Severity: wishlist
Owner: Klee Dienes
* Package name: iniparser
Version : 3.1-1
Upstream Author : Nicolas Devillard
* URL : http://ndevilla.free.fr/iniparser
* License : Expat
Programming Lang: C
Description : a stand-alone INI file readi
13 matches
Mail list logo
