media-plugins/kipi-plugins: Bump

git-svn-id: https://svn.disconnected-by-peer.at/svn/linamh/trunk/linamh@608 6952d904-891a-0410-993b-d76249ca496b

media-plugins/kipi-plugins/ChangeLog

@@ -0,0 +1,67 @@
+# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# Copyright 1999-2006 Gentoo Foundation; Distributed under the GPL v2
+# $Header: $
+
+*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+
+  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
+  Initial import.  Ebuild submitted by submitter_name <submitter_email>.
+  Note that the "changed_file" listing is optional if you are simply bumping
+  the rev of the ebuild and are only making changes to the .ebuild file
+  itself.  Also note that we now have a single unified paragraph rather than
+  having the first line separated from the rest by a newline.  Everything
+  should be in one block like this. (note by drobbins, 16 Jul 2002)
+
+  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
+  an earlier ChangeLog entry.
+ 
+-- Explanation of ChangeLog format:
+
+  ***************************************************************************
+  THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all
+  changes made to a set of ebuilds. That means that the most recent ChangeLog
+  entry *always* goes at the top of the file. More explanation below.
+  ***************************************************************************
+
+  ***************************************************************************
+  ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this
+  format and organize all changes under the "correct" "*" entry. This is not
+  correct. However, rather than making a concerted effort to fix these
+  ChangeLogs, we should spend our energy defining a comprehensive and strict
+  XML-based ChangeLog format which we then migrate to. But for any entries to
+  any ChangeLog that *you* make, please make sure to always add entries to the
+  top of the file like a good boy/girl. Even do this if it's clear that you're
+  adding an entry to a b0rked ChangeLog.
+  ***************************************************************************
+  
+  This changelog is targeted to users. This means that the comments should be
+  well explained and written in clean English.
+ 
+  Every new version or revision of the package should be marked by a '*'
+  separator line as above to indicate where in the chronology it was first
+  added to our CVS tree. Any changes since the last revision, really _any
+  changes at all_ have to be added to the top of the file, underneath the
+  initial copyright and cvs header comments, in exactly the same format as this
+  comment. If you are modifying older ebuilds, simply note them as changed
+  files and add your entry to the top of the ChangeLog. Resist the temptation
+  to "organize" your ChangeLog entries by placing them under the "correct" "*"
+  entries -- this isn't the purpose of the "*" entries.
+  
+  This means that you start with header line that has the following format,
+  indented two spaces:
+  
+  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
+  explanation should follow. It should be indented and wrapped at a line width
+  of 80 characters.  The changed_files can be omitted if they are obvious; for
+  example, if you are only modifying the .ebuild file and committing a new rev
+  of a package.  Any details about what exactly changed in the code should be
+  added as a message when the changes are committed to cvs, not in this file.
+
+-- A word regarding credit:
+
+  Please add credit information ("ebuild submitted by ...", "patch submitted
+  by ...") to the ChangeLog. Do not add this information to the ebuilds
+  themselves.
+
+  And remember: Give credit where credit is due. We're all doing this for
+  free, so the best we can hope (and expect!) to receive is credit.

media-plugins/kipi-plugins/Manifest

@@ -1,4 +1,4 @@
 AUX kipi-plugins-20081006-fix.patch 2736 RMD160 44c6e228a4436fa83a42f5a3e13156100b1aa1ff SHA1 53b1bee2c7ea19cc1f863b1fbebbb8235e2724a1 SHA256 da4eb5fdf01a0e7c3f415752ce73d429578f3c6814c38260927e77a38aa49784
-EBUILD kipi-plugins-20081127.ebuild 2769 RMD160 161132a4b27e8d77b2e114906b0d60d0f66e1323 SHA1 277169d4e68252deddcb686ac7feb20a534bae92 SHA256 6ff2bab054542fe23867f20920914016ee0d2c0422c61cea60c3f808b747d365
-MISC ChangeLog 0 RMD160 9c1185a5c5e9fc54612808977ee8f548b2258d31 SHA1 da39a3ee5e6b4b0d3255bfef95601890afd80709 SHA256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
+EBUILD kipi-plugins-20081208.ebuild 2782 RMD160 a7830a9778c407c46dfaebbcc2a1b70bc058aa5a SHA1 e0c77874ecccbb2875ef08a03e591f0c1778fe45 SHA256 4dc278c79d14614b5ca1e13f954a1f57d10957a4a5105ee24997292f02970f72
+MISC ChangeLog 3666 RMD160 68814a1b858c15df920dca2a6c0379a9fcc02b30 SHA1 88e132ba386897bc1eeef43f5aaa707f9ba0fa8c SHA256 5c13300278ea7b403d30ae138d73c7855126cd6ecb542059276c59d66f77dd74
 MISC metadata.xml 492 RMD160 012e23d9aa6da182cf0d3ad1e744eee999e14f48 SHA1 e706b077970bd64bf96429c694567710741a3a3e SHA256 fb0b7ef4457e7fc25ea0bf2b9837434e5cfe0352719149945438227134bb1bbb

media-plugins/kipi-plugins/kipi-plugins-20081208.ebuild

@@ -8,7 +8,7 @@ KMNAME="extragear/graphics"
 NEED_KDE="4.2"
 OPENGL_REQUIRED="optional"
 
-inherit kde4svn eutils
+inherit kde4-base subversion eutils
 
 ESVN_REPO_URI="svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/${PN}@{${PV}}"