From ff56ab67a56972d1f766a3bb02278b748982e998 Mon Sep 17 00:00:00 2001 From: Sven Eden Date: Tue, 29 Mar 2011 17:38:00 +0200 Subject: Everything digested. ChangeLogs and metadata.xml files will be updated tomorrow. --- www-apps/dotproject/ChangeLog | 68 +++------------------------------------- www-apps/dotproject/Manifest | 3 +- www-apps/dotproject/metadata.xml | 31 +----------------- 3 files changed, 8 insertions(+), 94 deletions(-) (limited to 'www-apps') diff --git a/www-apps/dotproject/ChangeLog b/www-apps/dotproject/ChangeLog index 6eff27d..4bca894 100644 --- a/www-apps/dotproject/ChangeLog +++ b/www-apps/dotproject/ChangeLog @@ -1,67 +1,9 @@ -# ChangeLog for / +# ChangeLog for www-apps/dotproject # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 # $Header: $ -*-- (DD MMM YYYY) +*dotproject-2.1.5-r1 (27 Mar 2011) - DD MMM YYYY; YOUR_NAME changed_file1, changed_file2 : - Initial import. Ebuild submitted by submitter_name . - 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 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 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. + 27 Mar 2011; Sven Eden +dotproject-2.1.5-r1.ebuild : + Initial commit of the ebuild. Simple version bump until the tree is + updated. diff --git a/www-apps/dotproject/Manifest b/www-apps/dotproject/Manifest index 95fcba1..4a49d37 100644 --- a/www-apps/dotproject/Manifest +++ b/www-apps/dotproject/Manifest @@ -1,4 +1,5 @@ AUX install-en.txt 793 RMD160 52b90aafed335845122e2117ae8c3fb510c1693d SHA1 2590df3221c75e80c967880069325edb5a038c6d SHA256 3745e3a4d5b9a642c9f409a8c09dc072787b687531f9adcfe31ea317bd3f7889 DIST dotproject-2.1.5.tar.gz 4524714 RMD160 d50f3b0ffd5fb390385b2c88420e660549696ca6 SHA1 89f80792bcf7344cb89142db614c7b34f8c67463 SHA256 86beef3a1280c3c2eccde6abe8ea0570e348fdecf756b581382fa8ad9aa331bf EBUILD dotproject-2.1.5-r1.ebuild 1316 RMD160 f92be242c7bcdc7ef8fa502cfe6d34e055e096f7 SHA1 25217e364d181c0e883bdfecc2b5a37c5152063a SHA256 9dcf2a302a52f03d7310b3f0599086703c315bed3ac6a922b9696f4ce4026390 -MISC dotproject-2.1.5-r1.ebuild~ 1339 RMD160 fcf9020a1836f9a755d9c7d6a9b5635b619e4d68 SHA1 c1e0aa7f56b18998fb73601ee138b7aa8f50aa3a SHA256 514c4ecc4faf8fdba03a73220fb0f8dbac6ae0294b1c834a14f4e3253b63c3e2 +MISC ChangeLog 311 RMD160 8df61739111a8ed0fbb364852dd26943407ce572 SHA1 2f27231fd326a7f587a973c3d46669d848dae07f SHA256 1870dbb73c966bf09e61f0d3c243500d9789c148975e9f902eb908adb3e8aa97 +MISC metadata.xml 162 RMD160 0b015f5ff17c4d8e7aee826d48b326cc19b1fed4 SHA1 671b30dafbea01228c8bb606af451a0795922840 SHA256 84ff2fc6c9a4af1b9dbe32aa81ab84c2958bc1bd65a9977686df2dcab6e420d0 diff --git a/www-apps/dotproject/metadata.xml b/www-apps/dotproject/metadata.xml index 46a44e5..6632069 100644 --- a/www-apps/dotproject/metadata.xml +++ b/www-apps/dotproject/metadata.xml @@ -1,34 +1,5 @@ - -no-herd - - @gentoo.org - - - - + web-apps -- cgit v1.2.3-65-gdbad