Ok, what would be the best way then? I don't want my efforts to be wasted,  
but am certainly not a C coder.


On Fri, 22 Jan 2016 17:23:51 +0100, Michael Tremer  
<michael.tremer(a)ipfire.org> wrote:

> No, that code has been dropped and pakfire was rewritten in C and
> Python. So there is no code shared.
>
> -Michael
>
> On Fri, 2016-01-22 at 17:22 +0100, Larsen wrote:
>> Ah ok, found it. Thanks!
>>
>> Will the code from pakfire2 (if I change anything) be used for
>> pakfire3 as
>> well?
>>
>>
>> Lars
>>
>>
>>
>> On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer
>> <michael.tremer(a)ipfire.org> wrote:
>>
>> > Hey,
>> >
>> > what you are looking at there is the source code of Pakfire 3. The
>> > code
>> > of the version that is running in IPFire 2 is here:
>> >
>> > http://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=src/pakfire;h=4894
>> > 6826ad9888dd39760783268566fe904de70d;hb=HEAD
>> >
>> > -Michael
>> >
>> > On Fri, 2016-01-22 at 16:13 +0100, Larsen wrote:
>> > > Hi,
>> > >
>> > > I wanted to see if I could add a command line parameter to tell
>> > > pakfire to
>> > > be more verbose, instead of silently putting its output into
>> > > "/var/log/pakfire/update-core-upgrade-##.log".
>> > > I have cloned the repository
>> > > https://github.com/ipfire/pakfire.git bu
>> > > t
>> > > cannot find one of the other params (non-interactive, no-colors)
>> > > in
>> > > the
>> > > code.
>> > >
>> > > What am I doing wrong?
>> > >
>> > >
>> > > Lars