From: "Nirbheek Chauhan" <nirbheek@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: dev-util/devhelp/
Date: Wed, 13 Apr 2011 09:57:02 +0000 (UTC) [thread overview]
Message-ID: <c5612f24c11a16fac5cb635e6a21a05fe37efc99.nirbheek@gentoo> (raw)
commit: c5612f24c11a16fac5cb635e6a21a05fe37efc99
Author: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 13 09:56:21 2011 +0000
Commit: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
CommitDate: Wed Apr 13 09:56:21 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=c5612f24
dev-util/devhelp: don't remove older notify calls
* Otherwise users can upgrade and forget to remove older libraries
---
dev-util/devhelp/devhelp-3.0.0.ebuild | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/dev-util/devhelp/devhelp-3.0.0.ebuild b/dev-util/devhelp/devhelp-3.0.0.ebuild
index 12336ee..f47bfec 100644
--- a/dev-util/devhelp/devhelp-3.0.0.ebuild
+++ b/dev-util/devhelp/devhelp-3.0.0.ebuild
@@ -52,7 +52,8 @@ pkg_postinst() {
gnome2_pkg_postinst
python_need_rebuild
python_mod_optimize /usr/$(get_libdir)/gedit/plugins
- # Keep this around so that users get reminded to delete this
+ # Keep all the notify calls around so that users get reminded to delete them
+ preserve_old_lib_notify /usr/$(get_libdir)/libdevhelp-1.so.1
preserve_old_lib_notify /usr/$(get_libdir)/libdevhelp-2.so.1
}
next reply other threads:[~2011-04-13 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 9:57 Nirbheek Chauhan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 8:00 [gentoo-commits] proj/gnome:master commit in: dev-util/devhelp/ Mart Raudsepp
2018-05-27 12:51 Gilles Dartiguelongue
2015-05-08 21:54 Gilles Dartiguelongue
2014-11-30 19:03 Remi Cardona
2014-04-24 22:35 Gilles Dartiguelongue
2014-04-12 15:44 Gilles Dartiguelongue
2013-12-01 23:18 Gilles Dartiguelongue
2013-11-14 22:52 Gilles Dartiguelongue
2012-11-18 19:33 Gilles Dartiguelongue
2012-10-27 21:22 Gilles Dartiguelongue
2011-04-13 5:52 Gilles Dartiguelongue
2011-04-05 0:57 Nirbheek Chauhan
2011-03-23 5:20 Nirbheek Chauhan
2011-03-09 11:34 Nirbheek Chauhan
2011-02-22 15:14 Nirbheek Chauhan
2011-02-09 20:13 Nirbheek Chauhan
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=c5612f24c11a16fac5cb635e6a21a05fe37efc99.nirbheek@gentoo \
--to=nirbheek@gentoo.org \
--cc=gentoo-commits@lists.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