From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: pakfire --verbose
Date: Fri, 22 Jan 2016 17:22:15 +0100 [thread overview]
Message-ID: <op.ybnefdaicahio0@atl-uetersen.atlantisgmbh.local> (raw)
In-Reply-To: <1453477951.585.28.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
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=48946826ad9888dd39760783268566fe904de70d;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
next prev parent reply other threads:[~2016-01-22 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:13 Larsen
2016-01-22 15:52 ` Michael Tremer
2016-01-22 16:22 ` Larsen [this message]
2016-01-22 16:23 ` Michael Tremer
2016-01-22 17:08 ` Larsen
2016-01-22 17:10 ` Michael Tremer
2016-01-22 17:48 ` Larsen
2016-01-22 18:01 ` Michael Tremer
2016-01-22 20:09 ` Larsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.ybnefdaicahio0@atl-uetersen.atlantisgmbh.local \
--to=larsen007@web.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox