public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: New ebuild metadata to mark how robust the package is?
Date: Sun, 18 Oct 2009 00:10:51 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.10.18.00.10.51@cox.net> (raw)
In-Reply-To: 200910170953.40078.patrick@gentoo.org

Patrick Lauer posted on Sat, 17 Oct 2009 09:53:39 +0200 as excerpted:

> On Saturday 17 October 2009 01:29:00 Daniel Bradshaw wrote:
>> Some packages, like findutils, are pretty robust and generally just get
>> on with working.
>> Other packages, like apache and ssh, need are more fragile and need
>> plenty of configuration.
> That's almost completely user-side configuration outside the influence
> of portage. emerge findutils and emerge apache "works" the same ...
> 
> 
>> Packages from the second group want emerging on their own, or in small
>> groups, the better to keep an eye out for notices about things that
>> might break, to update configs, and to check that they're running
>> happily.
> That's a very individual thing :)
> Sometimes apache is a critical service, sometimes apache is just there
> as a fallback if/when the lighttpd+php+... stack breaks.

FWIW, there's a portage helper package, IDR the name as I have my own 
system for this but it looks like it might be helpful here, that allows 
users to pick and choose their updates.  One could run it multiple times, 
updating (what the user considers) the critical stuff on its own, and 
updating everything else in a big bunch.

That seems like the answer here; it already exists; and it's in the tree 
(unless it has been removed recently, I don't know as IDR the name).  
Take a look thru app-portage and see what you find.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2009-10-18  0:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1255733421-30950-mlmmj-4f4db363@lists.gentoo.org>
2009-10-16 23:29 ` [gentoo-dev] New ebuild metadata to mark how robust the package is? Daniel Bradshaw
2009-10-16 23:48   ` Jeremy Olexa
2009-10-17  0:50   ` [gentoo-dev] " Ryan Hill
2009-10-17  5:33   ` [gentoo-dev] " Rémi Cardona
2009-10-17  9:27     ` Tobias Klausmann
2009-10-17  9:47       ` Petteri Räty
2009-10-17  7:53   ` Patrick Lauer
2009-10-18  0:10     ` Duncan [this message]
2009-10-21 12:45       ` [gentoo-dev] " Ladislav Laska
2009-10-21 15:21         ` Ladislav Laska
2009-10-21 16:30           ` William Hubbs
2009-10-26 12:55             ` Ladislav Laska
2009-10-26 21:49               ` Duncan

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=pan.2009.10.18.00.10.51@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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