From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: pakfire --verbose
Date: Fri, 22 Jan 2016 18:01:15 +0000 [thread overview]
Message-ID: <1453485675.585.35.camel@ipfire.org> (raw)
In-Reply-To: <op.ybnifaptcahio0@honk.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2575 bytes --]
Pakfire 3 works very different. So there is verbose output.
You can download the latest image to from over here to have a look:
http://people.ipfire.org/~stevee/IPFire_3.x/VM-Images/20151101/x86_64/
-Michael
On Fri, 2016-01-22 at 18:48 +0100, Larsen wrote:
> The best way to get this improvement into both versions? Or will
> pakfire3
> already have such a verbose param?
>
>
> On Fri, 22 Jan 2016 18:10:58 +0100, Michael Tremer
> <michael.tremer(a)ipfire.org> wrote:
>
> > The best way for doing what?
> >
> > On Fri, 2016-01-22 at 18:08 +0100, Larsen wrote:
> > > 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/pakfir
> > > > > > e;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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-22 18:01 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
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 [this message]
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=1453485675.585.35.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--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