Quoth Polytropon on Tuesday, 27 July 2010:
> On Tue, 27 Jul 2010 07:16:15 +0200, claudiu vasadi
> wrote:
>
> Finally, when I want to test out new features, both in OS and
> applications, I usually go with "bleeding edge". I'm often
> surprised to see how well things do work.
>
That's my experi
On Jul 27, 2010, at 10:53 AM, Polytropon wrote:
For servers, especially where I run critical apps, I follow the
bugs and announce lists (of the installed programs) to decide if
an update is required due to security reasons, then I update.
I find the VuXML FreeBSD RSS feed to be quite handy for
On Tue, 27 Jul 2010 07:16:15 +0200, claudiu vasadi
wrote:
> Hello fellas,
>
> I was wondering about your update strategy. Do you update your apps as soon
> as a new version is available in the ports ? Or do you follow the "if it
> works, don't touch it" strategy ?
I think you will get similar a
>I was wondering about your update strategy. Do you update your apps as soon
>as a new version is available in the ports ? Or do you follow the "if it
>works, don't touch it" strategy ?
>
There is no one strategy that pleases everyone. You'll have to
consider the time required to perform updates
I was wondering about your update strategy. Do you update your apps as soon
as a new version is available in the ports ? Or do you follow the "if it
works, don't touch it" strategy ?
I'm guessing "portupgrade" is your preferred way of doing this hence, do you
also choose -P or -PP ?
I update
Hello fellas,
I was wondering about your update strategy. Do you update your apps as soon
as a new version is available in the ports ? Or do you follow the "if it
works, don't touch it" strategy ?
I'm guessing "portupgrade" is your preferred way of doing this hence, do you
also choose -P or -PP ?
