From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: Comments regarding the upgrade process
Date: Tue, 22 Dec 2015 23:45:19 +0100 [thread overview]
Message-ID: <op.x92hhtkhcahio0@honk.fritz.box> (raw)
In-Reply-To: <1450823795.2928.14.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Tue, 22 Dec 2015 23:36:35 +0100, Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> Hi,
>
> I am afraid that I must disappoint you on some of these points. pakfire
> in IPFire 2 is legacy code and I do not have the time to add new
> features. It is just maintained as it is and bugs are fixed.
>
> We have a rewrite of this in IPFire 3 already.
So, there will be more verbose output?
>> PAKFIRE UPGR: We are going to install all packages listed above.
>> PAKFIRE INFO: Is this okay? [y/N]
>>
>> --> Shouldn't the default be Yes?
>
> Why?
Cause you would normally want to install the new packages? And maybe
IPFire relies on the new versions? (I don't know how this is supposed to
work)
Lars
next prev parent reply other threads:[~2015-12-22 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 18:16 Lars Schuhmacher
2015-12-22 22:36 ` Michael Tremer
2015-12-22 22:45 ` Larsen [this message]
2015-12-22 22:51 ` Michael Tremer
2015-12-22 23:25 ` Larsen
2015-12-23 0:35 ` R. W. Rodolico
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.x92hhtkhcahio0@honk.fritz.box \
--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