From: "Daniel Campbell" <zlg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/astyle/
Date: Tue, 26 Jan 2016 00:50:58 +0000 (UTC) [thread overview]
Message-ID: <1453769445.cab07b2c7b1884cccec00cdcf84b795076ea3755.zlg@gentoo> (raw)
commit: cab07b2c7b1884cccec00cdcf84b795076ea3755
Author: Daniel Campbell <zlg <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 26 00:47:58 2016 +0000
Commit: Daniel Campbell <zlg <AT> gentoo <DOT> org>
CommitDate: Tue Jan 26 00:50:45 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cab07b2c
dev-util/astyle: Take ownership of package
Package-Manager: portage-2.2.26
dev-util/astyle/metadata.xml | 49 ++++++++++++++++----------------------------
1 file changed, 18 insertions(+), 31 deletions(-)
diff --git a/dev-util/astyle/metadata.xml b/dev-util/astyle/metadata.xml
index c08bb1e..8770e9d 100644
--- a/dev-util/astyle/metadata.xml
+++ b/dev-util/astyle/metadata.xml
@@ -1,35 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <longdescription>
- From the web page:
-
- Artistic Style is a reindenter and reformatter of C++, C and Java source
- code.
-
- When indenting source code, we as programmers have a tendency to use both
- spaces and tab characters to create the wanted indentation. Moreover, some
- editors by default insert spaces instead of tabs when pressing the tab key,
- and other editors (Emacs for example) have the ability to "pretty up" lines
- by automatically setting up the white space before the code on the line,
- possibly inserting spaces in a code that up to now used only tabs for
- indentation.
-
- Since the NUMBER of space characters showed on screen for each tab character
- in the source code changes between editors (until the user sets up the
- number to his liking...), one of the standard problems facing programmers
- when moving from one source code editor to another is that code containing
- both spaces and tabs that was up to now perfectly indented, suddenly becomes
- a mess to look at when changing to another editor. Even if you as a
- programmer take care to ONLY use spaces or tabs, looking at other peoples
- source code can still be problematic.
-
- To address this problem I have created Artistic Style - a series of filters,
- written in C++, that automatically reindent & reformat C/C++/Java source
- files. These can be used from a command line, or it can be incorporated as
- classes in another C++ program.
- </longdescription>
- <upstream>
- <remote-id type="sourceforge">astyle</remote-id>
- </upstream>
+ <maintainer type="person">
+ <email>zlg@gentoo.org</email>
+ <name>Daniel Campbell</name>
+ </maintainer>
+ <longdescription>
+ astyle is a code formatter for C, C++, and Java source code, with many
+ granular formatting options to assist in enforcing code formatting
+ standards in projects.
+ </longdescription>
+ <upstream>
+ <maintainer status="active" type="person">
+ <email>jimp03@email.com</email>
+ <name>Jim Pattee</name>
+ </maintainer>
+ <remote-id type="sourceforge">astyle</remote-id>
+ <bugs-to>https://sourceforge.net/p/astyle/bugs/</bugs-to>
+ <doc>http://astyle.sourceforge.net/astyle.html</doc>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2016-01-26 0:51 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 0:50 Daniel Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 6:41 [gentoo-commits] repo/gentoo:master commit in: dev-util/astyle/ Arthur Zamarin
2025-04-26 1:45 Sam James
2025-04-26 1:02 Sam James
2025-04-26 0:43 Sam James
2025-04-26 0:32 Sam James
2025-03-10 2:21 Sam James
2025-03-10 2:21 Sam James
2024-11-09 13:24 Arthur Zamarin
2024-11-09 10:06 Arthur Zamarin
2024-11-09 2:14 Sam James
2024-11-09 2:14 Sam James
2024-09-11 15:31 Alfredo Tupone
2024-08-03 6:19 Joonas Niilola
2024-08-03 6:17 Joonas Niilola
2024-08-02 16:19 Sam James
2024-08-02 16:19 Sam James
2024-08-02 16:19 Sam James
2024-08-02 13:45 Viorel Munteanu
2024-08-02 13:45 Viorel Munteanu
2024-08-02 13:45 Viorel Munteanu
2023-10-20 0:51 Sam James
2023-09-24 4:39 Sam James
2023-09-24 4:39 Sam James
2023-08-30 7:48 Sam James
2023-08-30 7:48 Sam James
2023-06-19 21:28 Sam James
2023-01-23 2:30 Matthias Maier
2023-01-23 2:30 Matthias Maier
2021-02-05 12:29 Sam James
2021-02-02 21:02 Sam James
2020-02-26 18:25 Andreas Sturmlechner
2018-10-24 7:34 Mikle Kolyada
2018-10-17 12:07 Thomas Deutschmann
2018-08-08 10:03 Guilherme Amadio
2018-05-29 0:41 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-05-28 22:17 Matthias Maier
2018-03-06 17:44 Amy Liffey
2018-03-06 16:08 Amy Liffey
2018-02-07 0:54 Matthias Maier
2017-12-19 6:50 Matthias Maier
2017-12-12 21:46 Daniel Campbell
2017-08-29 23:16 Thomas Deutschmann
2017-07-31 12:56 Tobias Klausmann
2017-07-30 10:57 Sergei Trofimovich
2017-06-23 19:39 Daniel Campbell
2017-06-18 6:23 Daniel Campbell
2017-06-18 6:23 Daniel Campbell
2017-01-02 14:36 Daniel Campbell
2016-03-18 19:11 Michał Górny
2016-03-06 22:20 Daniel Campbell
2015-08-26 11:00 Agostino Sarubbo
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=1453769445.cab07b2c7b1884cccec00cdcf84b795076ea3755.zlg@gentoo \
--to=zlg@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