From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New ebuild metadata to mark how robust the package is?
Date: Sat, 17 Oct 2009 12:47:29 +0300 [thread overview]
Message-ID: <4AD992B1.6060706@gentoo.org> (raw)
In-Reply-To: <20091017092718.GA13018@eric.schwarzvogel.de>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Tobias Klausmann wrote:
>
> Come to think of it, how about an ewarn/einfo that is only
> triggered on fresh installs, but not on upgrades? You can still
> warn that foobard needs an etc-update and a restart, but I don't
> need to be reminded where the examples are every time.
>
> Ideally, one would be an einfo and one an ewarn, but in my
> experience, many messages are ewarns "to be safe" (or so I
> suspect).
>
With EAPI 3 easy to add wrappers around e* using REPLACING_VERSIONS and
REPLACED_BY_VERSION.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2009-10-17 9:47 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 [this message]
2009-10-17 7:53 ` Patrick Lauer
2009-10-18 0:10 ` [gentoo-dev] " Duncan
2009-10-21 12:45 ` 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=4AD992B1.6060706@gentoo.org \
--to=betelgeuse@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