From: Ambroz Bizjak <ambrop7@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: minimalistic emerge
Date: Sat, 9 Aug 2014 14:16:04 +0200 [thread overview]
Message-ID: <CAOA3yKLFCArZ83h4gK0LCqg-+Af_pdc-BwK5X08wxedMWUx7ww@mail.gmail.com> (raw)
In-Reply-To: <53E600A7.9000805@gentoo.org>
Hey all.
Regarding updates breaking the system, NixOS might be worth a try.
The functional nature of the package manager there lets you try out an
update, either live or in a VM, as well as roll back to the old
configuration in case of problems. Due to the design there's no risk
in building updates on a stable system, the build process won't
interfere until all the updates are built and you decide to try it out
in some way (other by exhausting RAM etc).
They also have both stable release branches and a master branch with
more updated packages.
(Not trying to start a distro war, please excuse me if it sounds like this.)
Best regards,
Ambroz
On Sat, Aug 9, 2014 at 1:06 PM, hasufell <hasufell@gentoo.org> wrote:
> Duncan:
>> Peter Stuge posted on Sat, 09 Aug 2014 10:34:58 +0200 as excerpted:
>>
>>> Duncan wrote:
>>>> Red Hat is the gold standard, very long term commercial support,
>>>> IIRC 10 years, and very good community relations
>>>
>>> I've heard this on occasion, but reality is actually quite different.
>>>
>>> Red Hat is a software service provider. They do whatever their paying
>>> customers ask for. They do not take community relations very seriously
>>> in my experience. I believe it is the job of a single person.
>>
>
> [...]
>
> Can you open a new thread about redhat? I fail to see any connection to
> the initial issue.
>
prev parent reply other threads:[~2014-08-09 12:16 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:12 [gentoo-dev] minimalistic emerge Igor
2014-08-08 13:22 ` Ciaran McCreesh
2014-08-08 15:23 ` Igor
2014-08-08 15:36 ` hasufell
2014-08-08 15:53 ` Igor
2014-08-08 15:45 ` Ian Stakenvicius
2014-08-08 16:27 ` Igor
2014-08-08 16:40 ` Homer Parker
2014-08-08 17:26 ` Igor
2014-08-08 17:32 ` Homer Parker
2014-08-08 17:30 ` Ian Stakenvicius
2014-08-09 9:34 ` "Paweł Hajdan, Jr."
2014-08-09 15:25 ` Igor
2014-08-13 7:54 ` [OT] " Tom Wijsman
2014-08-08 16:31 ` Rich Freeman
2014-08-08 13:23 ` hasufell
2014-08-08 13:32 ` Jeroen Roovers
2014-08-08 15:14 ` Alan McKinnon
2014-08-13 8:13 ` Tom Wijsman
2014-08-08 15:51 ` Kent Fredric
2014-08-08 16:58 ` Igor
2014-08-08 17:29 ` Kent Fredric
2014-08-08 20:52 ` Igor
2014-08-08 21:33 ` Kent Fredric
2014-08-08 21:39 ` Ian Stakenvicius
2014-08-08 21:43 ` Kent Fredric
2014-08-09 14:56 ` Igor
2014-08-09 15:12 ` Chris Reffett
2014-08-09 17:10 ` Ciaran McCreesh
2014-08-13 8:20 ` Tom Wijsman
2014-08-13 13:17 ` hasufell
2014-08-09 19:30 ` Jeroen Roovers
2014-08-09 15:44 ` Chris Reffett
2014-08-09 15:46 ` Chris Reffett
2014-08-09 15:58 ` Chris Reffett
2014-08-08 19:34 ` Peter Stuge
2014-08-08 19:47 ` Ian Stakenvicius
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman
2014-08-09 8:30 ` Peter Stuge
2014-08-08 21:04 ` Johannes Huber
2014-08-13 8:25 ` Tom Wijsman
2014-08-09 3:07 ` [gentoo-dev] " Duncan
2014-08-09 8:34 ` Peter Stuge
2014-08-09 11:03 ` Duncan
2014-08-09 11:06 ` hasufell
2014-08-09 12:16 ` Ambroz Bizjak [this message]
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=CAOA3yKLFCArZ83h4gK0LCqg-+Af_pdc-BwK5X08wxedMWUx7ww@mail.gmail.com \
--to=ambrop7@gmail.com \
--cc=gentoo-dev@lists.gentoo.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