public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian D. Harring" <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: upgrade's and rc-scripts
Date: Fri, 22 Jul 2005 18:40:54 -0500	[thread overview]
Message-ID: <20050722234054.GA12683@exodus> (raw)
In-Reply-To: <42E17F33.6050709@upb.de>

[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]

On Sat, Jul 23, 2005 at 01:20:19AM +0200, Sven Köhler wrote:
> > Out of curiousity, has any put any thought into some automated method 
> > or hook for allowing restarting of rc-scripts on upgrade/re-emerge of 
> > a package?
> > 
> > Other question is if any such hook is even needed.
> > So... thoughts?  I don't really have any input on it, aside from I'd 
> > like to gather what people want/think would be useful.
> 
> Another good idea, would be "pending jobs" list. Many ebuilds provide
> imports instructions like "you can now delete this or that config-file"
> or like "you must immediatly run this or that".
>
> These usually scroll by while there're nobody watching the screen and/or
> they cannot be read completely, since they scroll away too fast.
logging (and post display) of info/warning, it's in head.
 
> Apropos config-files: what about config-files that are provided by the
> old-version of an ebuild but have been moved or removed by the new
> version? etc-update doesn't know about them. So /etc/ will be full of
> useless config-files after some time.
Vapier had suggested yanking (on unmerge, not replacement) any 
config_protected file that has the same md5/mtime as what it was 
originally merged with.

This would cause issues for nvidia-kernel though I'd think, although 
their solution isn't exactly optimal (no better solution atm either 
though).
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-22 23:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 21:54 [gentoo-dev] upgrade's and rc-scripts Brian D. Harring
2005-07-20 22:10 ` Chris Gianelloni
2005-07-20 22:24   ` Brian D. Harring
2005-07-20 22:23 ` Mike Frysinger
2005-07-21 12:10   ` Zac Medico
2005-07-22  9:01     ` [gentoo-dev] " Duncan
2005-07-22 15:52       ` Zac Medico
2005-07-22 21:50         ` [gentoo-dev] " Duncan
2005-07-22 23:20 ` [gentoo-dev] " Sven Köhler
2005-07-22 23:40   ` Brian D. Harring [this message]
2005-07-24 13:25     ` Martin Schlemmer
2005-08-25 11:59       ` Paul de Vrieze
2005-07-27 13:44     ` Nathan L. Adams
2005-07-29 13:08   ` Enrico Horn

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=20050722234054.GA12683@exodus \
    --to=ferringb@gentoo.org \
    --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