From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larsen To: development@lists.ipfire.org Subject: Re: pakfire --verbose Date: Fri, 22 Jan 2016 17:22:15 +0100 Message-ID: In-Reply-To: <1453477951.585.28.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4829600299688169519==" List-Id: --===============4829600299688169519== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ah ok, found it. Thanks! Will the code from pakfire2 (if I change anything) be used for pakfire3 as =20 well? Lars On Fri, 22 Jan 2016 16:52:31 +0100, Michael Tremer =20 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=3Dipfire-2.x.git;a=3Dtree;f=3Dsrc/pakfire;h=3D4894= 6826ad9888dd39760783268566fe904de70d;hb=3DHEAD > > -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 --===============4829600299688169519==--